CVE-2026-89447

iommufd: Avoid locking internal accesses during unmap

Published Sep 11, 2026 CVSS 3.1 · 4.4 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw in the Linux kernel IOMMU daemon (iommufd) occurs during an unmap operation. If an internal access is encountered, the routine skips the normal unmap callback but still holds a lock on the bypassed object, causing the reference count for that object to remain incremented. The net effect is a reference counting leak that can cause memory usage to grow beyond what a normal unmap would expend (CWE-911).

Affected Systems

All Linux kernel releases that do not include the commit that resolves the issue (0dbcdf4473a614adbd732d567c9b39ac0e040e0c). Any distribution shipping a kernel unchanged by this patch and that loads the iommufd module for IOMMU handling is affected.

Risk and Exploitability

The CVSS score of 4.4 indicates moderate severity. The EPSS score is below 1 % and the vulnerability is not listed in the CISA KEV catalog, implying a very low probability of exploitation in the wild. The likely attack vector is privileged kernel access, as the vulnerable code path is exercised only by kernel components. The exposed leak may lead to incremental resource consumption, but no direct denial‑of‑service or privilege escalation vector is documented.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update your Linux kernel to 0dbcdf4473a614adbd732d567c9b39ac0e040e0c or later to close the reference count leak.
  • If a kernel upgrade is not possible, unload the iommufd module to prevent the vulnerable unmap logic from executing.
  • Observe system memory metrics and kernel logs for abnormal growth or frequent iommufd activity; apply general and patching other subsystems.

Generated by OpenCVE AI on September 21, 2026 at 01:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-911
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
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.
Title iommufd: Avoid locking internal accesses during unmap
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-911

    Improper Update of Reference Count

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 8:46 AM
Reserved
Sep 11, 2026, 7:38 PM
Status
Received
Published
Sep 11, 2026, 8:19 PM
Modified
Oct 19, 2026, 9:17 AM
Severity
Moderate
Public date
Sep 11, 2026, 7:43 PM