CVE-2026-99586 in Linuxinfo

Summary

by MITRE • 11/20/2026

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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel has addressed a critical hardware erratum affecting ARM System Memory Management Unit version 3, specifically identified as MMU-700 with issue numbers #3777127 and S3: #3673557. This vulnerability pertains to the handling of Contiguous Page Table Entries during invalidation operations within the IOMMU subsystem. The core technical flaw arises from a subtle interaction between the hardware's range invalidation generation algorithm and the software implementation of Shared Virtual Addressing, or SVA. While previous assumptions suggested that the driver always utilized range invalidation which would mitigate this issue, it was discovered that the erratum requires the invalidation range to fully enclose the entire contiguous grouping to be effective. The existing kernel logic did not guarantee this enclosure because two sequential range invalidations could have a split point falling inside a CONT grouping, thereby failing to prevent the hardware error condition associated with under-invalidation.

From an operational perspective, this vulnerability exposes systems using ARM SMMU v3 to potential stability and security risks when Shared Virtual Addressing is employed. The flaw can be triggered by malicious userspace applications that manipulate memory mappings through system calls such as mmap, mprotect, or munmap. By carefully crafting these operations, an attacker could induce a scenario where the TLB gather routines split invalidation ranges in the middle of a contiguous page table entry grouping. This results in incomplete cache coherency and potential data corruption or unauthorized access to memory regions that should have been properly invalidated. The impact is particularly severe because it involves the IOMMU, which acts as a gatekeeper for device-to-memory DMA transactions, meaning that bypassing these protections could lead to privilege escalation or information disclosure depending on the specific hardware configuration and driver interactions.

The remediation strategy implemented in this update focuses on ensuring that SVA invalidations utilize a simplified algorithm derived from recent TLB rework efforts. This new approach guarantees that a single range invalidation is issued for each MMU notifier callback, thereby ensuring that any possible contiguous grouping is fully covered by the invalidation command. The kernel now detects IOMMUs affected by this specific erratum and applies the corrected logic exclusively to those devices. Additionally, the errata list has been updated to include the S3 variation of the issue, allowing for more precise hardware-specific handling in future code paths. This fix aligns with industry best practices for mitigating hardware silicon defects through software workarounds, a common pattern observed in ARM architecture maintenance where kernel developers must account for subtle implementation details that differ from initial design assumptions.

In terms of security classification and standard mapping, this vulnerability relates to CWE-20 Improper Input Validation as the system fails to properly validate or align memory ranges before issuing hardware commands. It also touches upon CWE-367 Time-of-check Time-of-use race conditions in a broader sense due to the asynchronous nature of TLB invalidations relative to page table modifications. From an ATT&CK perspective, this falls under T1499 Endpoint Denial of Service if exploited for stability disruption or potentially T1055 Process Injection if leveraged to corrupt memory structures for code execution. Future development efforts should ensure that any addition of CONT support to iommu_domain page tables either adopts the one-invalidate-per-range algorithm established here or disables CONT support entirely in those contexts to prevent recurrence. Maintaining strict alignment between software invalidation ranges and hardware contiguous grouping boundaries is essential for preserving system integrity on ARM-based platforms utilizing SMMU v3.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00156

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!