CVE-2026-99586

published 20 Nov 2026 · updated 20 Nov 2026

iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 84c6089a365ff5547f9ea30cb407dc5fe3124fd3, Kernel 96ecddc5141c967c5a59fa85ccbdfdb3cec61209 and Kernel 7.3.5.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.10, >=3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3 <84c6089a365ff5547f9ea30cb407dc5fe3124fd3, >=3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3 <96ecddc5141c967c5a59fa85ccbdfdb3cec6120984c6089a365ff5547f9ea30cb407dc5fe3124fd3, 96ecddc5141c967c5a59fa85ccbdfdb3cec61209
linux-kernel: Kernel>=5.10.0 <7.3.57.3.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99586 severity on Zeptric[![CVE-2026-99586](https://zeptric.io/badge/cve/CVE-2026-99586.svg)](https://zeptric.io/cve/CVE-2026-99586)