CVE-2026-64152: iommu: Handle unmap error when iommu_debug is enabled
In the Linux kernel, the following vulnerability has been resolved:
iommu: Handle unmap error when iommudebug is enabled
Sashiko noticed a latent bug where the map error flow called iommuunmap() which calls iommudebugunmapbegin()/iommudebugunmapend() however since this is an error path the map flow never actually established the original iommudebugmap() it will malfunction.
Lift the unmap error handling into iommumapnosync() and reorder it so the tracemap()/iommudebugmap() records the partial mapping and then immediately unmaps it. This avoid creating the unbalanced tracking and provides saner tracing instead of a unmap unmatched to any map.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64152?
The severity of CVE-2026-64152 is high, with a CVSS score of 7.8.
How do I fix CVE-2026-64152?
To fix CVE-2026-64152, ensure that you update to the latest version of the Linux kernel where the vulnerability has been patched.
What impact does CVE-2026-64152 have on my system?
CVE-2026-64152 can potentially lead to heightened privileges for attackers due to improper handling of unmap errors.
Is CVE-2026-64152 relevant for all versions of the Linux kernel?
CVE-2026-64152 affects certain versions of the Linux kernel that have iommu_debug enabled, so it is essential to check your specific version.
Can CVE-2026-64152 lead to data exposure?
Yes, CVE-2026-64152 has the potential for data exposure due to its ability to compromise confidentiality and integrity.