All reports
Low

kernel: iommufd: Avoid locking internal accesses during unmap

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-89447

Probability of exploitation in the next 30 days: 0.22%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's iommufd subsystem. A local attacker could exploit a vulnerability where an object reference is leaked during the unmapping of internal accesses. This occurs because the iommufd_access_notify_unmap() function incorrectly locks an object before checking if the access is internal, leading to the object reference not being released. This resource leak could potentially lead to a denial of service.