Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
1 version affected across 1 product
🔴 #Linux Kernel, IOMMU Debug Unbalanced Tracking Vulnerability, #CVE-2026-64152 (HIGH) -DC-Aug2026-1568 https://dailycve.com/linux-kernel-iommu-debug-unbalanced-tracking-vulnerability-cve-2026-64152-high-dc-aug2026-1568/
Post summary
A new Linux kernel IOMMU debug vulnerability (CVE‑2026‑64152) has been disclosed with high severity, but no exploit, patch, or mitigation details are provided.
4 of 4 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| OS | linux | linux_kernel | - | - | - |
| OS | linux | linux_kernel | 7.1 | - | - |
| OS | linux | linux_kernel | 7.1 | - | - |
| OS | linux | linux_kernel | 7.1 | - | - |