CVE-2026-99586

Source
https://cve.org/CVERecord?id=CVE-2026-99586
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99586.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99586
Published
2026-11-20T05:49:16Z
Modified
2026-11-20T07:00:42Z
Summary
iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99586.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3f1ce8e85ee06dbe6a8b2e037e9b35f6b32e9ab3
Fixed
96ecddc5141c967c5a59fa85ccbdfdb3cec61209
Fixed
84c6089a365ff5547f9ea30cb407dc5fe3124fd3

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99586.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.10.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99586.json"