CVE-2026-64152

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.

Package Linux Kernel
Published 2026-07-19
Last modified 2026-07-19
Patch available
Yes

Affected versions

Linux kernel versions 7.0 and later are affected. Fixed in 7.0.11, 7.1 and their respective stable series.

Affected from
≥ 7.0
Fixed in
✓ 7.0.11 7.0.x ✓ 7.1

References

2 total

Frequently asked questions

  • What is CVE-2026-64152?

    CVE-2026-64152 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 7.0 onward and has been patched in 7.0.11 and 7.1. CVE-2026-64152 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64152?

    Yes — CVE-2026-64152 has been patched. Fixed versions include 7.0.11 and 7.1. If you are running Linux kernel 7.0 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64152 actively exploited?

    No — CVE-2026-64152 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Back to
All CVEs
View on
NVD / NIST