iommufd: Avoid locking internal accesses during unmap (CVE-2026-89447) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-89447

iommufd: Avoid locking internal accesses during unmap

Answer in brief

CVE-2026-89447 records a Unknown severity vulnerability in iommufd: Avoid locking internal accesses during unmap. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 11, 2026Updated Sep 11, 2026Source checked Sep 12, 2026First seen by HOL Sep 11, 2026Material review Sep 11, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <436189ee4bb2c7c993b945d68570dd38c3e4349e \|\| >=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <50a66a63d1c841ae6b28a4551f642c1bba4c9529 \|\| >=27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0 <0dbcdf4473a614adbd732d567c9b39ac0e040e0c	436189ee4bb2c7c993b945d68570dd38c3e4349e, 50a66a63d1c841ae6b28a4551f642c1bba4c9529, 0dbcdf4473a614adbd732d567c9b39ac0e040e0c
Linux/Linuxgeneric	6.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 436189ee4bb2c7c993b945d68570dd38c3e4349e if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 11, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: iommufd: Avoid locking internal accesses during unmap iommufd_access_notify_unmap() skips internal accesses because they do not have an external unmap callback to invoke. However, the current test calls iommufd_lock_obj() before checking whether the access is internal. If iommufd_lock_obj() succeeds, the loop then sees the internal access and continues, bypassing the matching iommufd_put_object() used by the normal unmap path. This leaks the object reference taken by iommufd_lock_obj(). Check for internal accesses first so skipped entries are never locked.

Quoted source text, attributed separately from HOL analysis.