CVE-2026-99586: iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA
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 iommudomain page tables should either use this one-invalidate/one-range invalidation algorithm or disable CONT support in the iommudomain.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Compensating control
For IOMMUs affected by the erratum, ensure each SVA range invalidation fully encloses the entire CONT PTE grouping and is not split within it; alternatively, disable CONT support in the iommu_domain.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue applies to ARM SMMU v3 implementations affected by MMU-700 erratum #3777127 or S3 erratum #3673557 when they use SVA to share a CPU page table containing CONT page-table entries. The description identifies SVA as the only current kernel user of CONT entries.
What condition causes the erratum to be triggered?
A vulnerable condition can occur when SVA invalidation processing splits an invalidation into multiple ranges and a split point falls within a CONT grouping. Two sequential range invalidations do not address the erratum when neither invalidation fully encloses that CONT grouping.
Why is use of range invalidation alone insufficient?
The hardware workaround requires one invalidation range that spans the entire CONT grouping. The SMMU range-invalidation generator can split one SVA invalidation request into several ranges, and the memory-management layer does not ensure those ranges are aligned to avoid splitting a CONT grouping.