CVE-2026-58801 · Infrastructure
NO FIX YET
A logic error in the arm-smmu-v3 driver's smmu_domain_config_s1 function can let code reach stale stream table entries after stream IDs are reassigned. An attacker with system-level privileges on the machine could read information they should not see.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems using an ARM SMMUv3 IOMMU with the arm-smmu-v3 kernel driver, where stream IDs get reassigned between devices. The sources do not say which kernel versions are affected or whether default configurations are exposed. Systems without arm-smmu-v3 hardware can skip it.
Not affected if no-arm-smmu-v3-hardware
Who cares arm64, iommu, linux-kernel
Unknown from the sources.
No fix yet, per the sources.
In smmu_domain_config_s1 of arm-smmu-v3.c, there is a possible way to access stale stream table entries across reassigned stream identifiers due to a logic error. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.