In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent… (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.
AI Analysis
Technical Summary
CVE-2026-64152 addresses a latent bug in the Linux kernel's IOMMU code where, during an error in the mapping flow with iommu_debug enabled, the unmap error handling called unmap functions without a corresponding initial map call. This caused malfunction in the iommu_debug tracing due to unbalanced map/unmap tracking. The patch lifts the unmap error handling into iommu_map_nosync() and reorders operations so that partial mappings are recorded and immediately unmapped, ensuring balanced and accurate debug tracing.
Potential Impact
The vulnerability affects the integrity of iommu_debug tracing by causing unbalanced map/unmap operations during error handling. This could lead to incorrect debug information and potentially hinder debugging or system analysis. There is no indication of direct security impact such as privilege escalation or denial of service.
Mitigation Recommendations
A fix has been applied in the Linux kernel to address this issue. Users should update to the patched kernel versions once available. Since this is a kernel-level fix, applying the official kernel updates from the vendor or distribution is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: iommu: Handle unmap error when iommu_debug is enabled Sashiko noticed a latent… (CVE-2026-64152)
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 v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-64152 addresses a latent bug in the Linux kernel's IOMMU code where, during an error in the mapping flow with iommu_debug enabled, the unmap error handling called unmap functions without a corresponding initial map call. This caused malfunction in the iommu_debug tracing due to unbalanced map/unmap tracking. The patch lifts the unmap error handling into iommu_map_nosync() and reorders operations so that partial mappings are recorded and immediately unmapped, ensuring balanced and accurate debug tracing.
Potential Impact
The vulnerability affects the integrity of iommu_debug tracing by causing unbalanced map/unmap operations during error handling. This could lead to incorrect debug information and potentially hinder debugging or system analysis. There is no indication of direct security impact such as privilege escalation or denial of service.
Mitigation Recommendations
A fix has been applied in the Linux kernel to address this issue. Users should update to the patched kernel versions once available. Since this is a kernel-level fix, applying the official kernel updates from the vendor or distribution is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2cx2-4725-6r7g
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64152"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912b23f
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:46:55 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.