iommu: Handle unmap error when iommu_debug is enabled
Summary
| CVE | CVE-2026-64152 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-19 16:17:57 UTC |
| Updated | 2026-07-19 16:17:57 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected ccc21213f013834b484cdcc738e282f963fcfc97 0cd028806efc148a75d4acf711d21db335a89661 git |
Not specified |
| CNA |
Linux |
Linux |
affected ccc21213f013834b484cdcc738e282f963fcfc97 0735c54804c709d1b292f3b6947cfb560b2ce552 git |
Not specified |
| CNA |
Linux |
Linux |
affected 7.0 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.11 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/0735c54804c709d1b292f3b6947cfb560b2ce552 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0cd028806efc148a75d4acf711d21db335a89661 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.