CVE-2026-0178 · Infrastructure
NO FIX YET
In the arm-smmu-v3 driver, a logic error leaves stale stream table entries that can bypass direct memory access isolation. A local process with system-level execution privileges can escalate its privileges.
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 running Linux on ARM64 hardware that uses the Arm SMMUv3 IOMMU, where the arm-smmu-v3 driver is loaded. The sources do not name affected kernel versions or product ranges. Exploitation needs local code execution at system privilege, so machines without untrusted local users are at lower risk.
Not affected if no-arm-smmu-v3-hardware, x86-only-hosts
Who cares arm64, kernel, linux, smmu
Unknown from the sources.
No fix yet, per the sources.
In multiple functions of arm-smmu-v3.c, there is a possible way to bypass direct memory access isolation via stale stream table entries due to a logic error. This could lead to local escalation of privilege 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.