CVE-2026-89447

Unknown

Last modified

CVE-2026-89447 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0, < 436189ee4bb2c7c993b945d68570dd38c3e4349e; >= 27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0, < 50a66a63d1c841ae6b28a4551f642c1bba4c9529; >= 27b77ea5feaa8fcf385ea99ce757982b0ac9d1f0, < 0dbcdf4473a614adbd732d567c9b39ac0e040e0c
LinuxLinux6.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89447?
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.
How severe is CVE-2026-89447?
Severity scoring for CVE-2026-89447 is pending analysis.
How do I fix CVE-2026-89447?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-89447?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST