{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3"
            },
            {
              "fixed": "96ecddc5141c967c5a59fa85ccbdfdb3cec61209"
            },
            {
              "fixed": "84c6089a365ff5547f9ea30cb407dc5fe3124fd3"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.10.0"
            },
            {
              "fixed": "7.3.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99586.json"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA\n\nThe erratum (MMU-700: #3777127, S3: #3673557) deals with under\ninvalidation of a CONT PTE grouping in the SMMU. The recommended work\naround is to use a range invalidation that spans the entire CONT. The only\nuser of CONT in the kernel right now is through SVA sharing a CPU page\ntable that contains a CONT created by the mm.\n\nPreviously it was thought that this errata was dealt with because the\ndriver always uses range invalidation. However, there is a subtle detail\nin the errata that the invalidation range must fully enclose the entire\nCONT for it to work.\n\nIt seems that two sequential range invalidations, with a split point\nfalling inside a CONT grouping, will not prevent the errata.\n\nThe SMMU's range invalidation generation algorithm does not produce a\nsingle invalidation for a single SVA invalidation request, nor does the mm\ncarefully align the SVA invalidation ranges to accommodate the splitting\nof the invalidation into several ranges.\n\nThus, when processing a SVA invalidation, the range invalidation splitting\nroutine can generate a range invalidation that is split in the middle of\nthe CONT and risk under invalidation from this errata. This condition\ncould be triggered by a malicious userspace manipulating the TLB gathers\nvia mmap/mprotect/munmap.\n\nUpdate the errata list to the include the S3 variation, detect the IOMMUs\nthat have it, and then have SVA invalidations use a simplified version of\nthe over invalidation algorithm from the tlbi rework series. This ensures\nthat a single range invalidation is issued for a single MMU notifier\ncallback and now the range invalidation is guarenteed to cover any posible\nCONT.\n\nFuture work to add CONT to iommu_domain page tables should either use this\none-invalidate/one-range invalidation algorithm or disable CONT support in\nthe iommu_domain.",
  "id": "CVE-2026-99586",
  "modified": "2026-11-20T06:45:33.624038842Z",
  "published": "2026-11-20T05:49:16.304Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/84c6089a365ff5547f9ea30cb407dc5fe3124fd3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/96ecddc5141c967c5a59fa85ccbdfdb3cec61209"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99586.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99586"
    }
  ],
  "schema_version": "1.9.2",
  "summary": "iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA"
}