CVE-2026-99586
iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA
No exploitation reported by the sources we read.
- Published2026-11-20
- Fixed in7.3.5
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA The erratum (MMU-700: #3777127, S3: #3673557) deals with under invalidation of a CONT PTE grouping in the SMMU. The recommended work around is to use a range invalidation that spans the entire CONT. The only user of CONT in the kernel right now is through SVA sharing a CPU page table that contains a CONT created by the mm. Previously it was thought that this errata was dealt with because the driver always uses range invalidation. However, there is a subtle detail in the errata that the invalidation range must fully enclose the entire CONT for it to work. It seems that two sequential range invalidations, with a split point falling inside a CONT grouping, will not prevent the errata. The SMMU's range invalidation generation algorithm does not produce a single invalidation for a single SVA invalidation request, nor does the mm carefully align the SVA invalidation ranges to accommodate the splitting of the invalidation into several ranges. Thus, when processing a SVA invalidation, the range invalidation splitting routine can generate a range invalidation that is split in the middle of the CONT and risk under invalidation from this errata. This condition could be triggered by a malicious userspace manipulating the TLB gathers via mmap/mprotect/munmap. Update the errata list to the include the S3 variation, detect the IOMMUs that have it, and then have SVA invalidations use a simplified version of the over invalidation algorithm from the tlbi rework series. This ensures that a single range invalidation is issued for a single MMU notifier callback and now the range invalidation is guarenteed to cover any posible CONT. Future work to add CONT to iommu_domain page tables should either use this one-invalidate/one-range invalidation algorithm or disable CONT support in the iommu_domain.
Timeline
dates in UTC- 2026-11-2005:49CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 5.10.0, < 7.3.5 | 7.3.5 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3, < 96ecddc5141c967c5a59fa85ccbdfdb3cec61209fixed in 96ecddc5141c967c5a59fa85ccbdfdb3cec61209git
- ≥ 3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3, < 84c6089a365ff5547f9ea30cb407dc5fe3124fd3fixed in 84c6089a365ff5547f9ea30cb407dc5fe3124fd3git
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 5.10no fix stated
Not affected < 5.10 · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc1
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxDebian:14all versions · no fixed version listed
- linuxDebian:13all versions · no fixed version listed
- linuxDebian:12all versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.64-r0 · no fixed version listed
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
- linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed
Vendor advisories
kernel: kernel: arm-smmu-v3: unauthorized memory access via incomplete TLB range invalidation
kernel.src as a component of Red Hat Enterprise Linux 10 · bpftool as a component of Red Hat Enterprise Linux 9 · kernel as a component of Red Hat Enterprise Linux 9 · +110 more
Fix
- Update Linux kernel to 7.3.5
- No fix available, says the vendor Red Hat Product Security CVE-2026-99586 · 113 productsAffected
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.18.22026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-115324same flawAzure Linux · MIT
- EUVD-2026-131036same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-9rjq-6pqp-8j63same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- Published
- 2026-11-20
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-9rjq-6pqp-8j63
Frequently asked questions
What is CVE-2026-99586?
Is CVE-2026-99586 actively exploited?
What is the CVSS score for CVE-2026-99586?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-9rjq-6pqp-8j63
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0