Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent bug where the map error flow called iommu_unmap() which calls iommu_debug_unmap_begin()/iommu_debug_unmap_end() however since this is an error path the map flow never actually established the original iommu_debug_map() it will malfunction. Lift the unmap error handling into iommu_map_nosync() and reorder it so the trace_map()/iommu_debug_map() 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 7.0, < 7.0.11 |
References
- https://git.kernel.org/stable/c/0735c54804c709d1b292f3b6947cfb560b2ce552Patch
- https://git.kernel.org/stable/c/0cd028806efc148a75d4acf711d21db335a89661Patch
FAQ
What is CVE-2026-64152?
CVE-2026-64152 is a vulnerability with a CVSS score of 7.8 (HIGH). In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent bug where the map error flow called iommu_unmap() w...
How severe is CVE-2026-64152?
CVE-2026-64152 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-64152?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.