CVE-2026-89447 Linux CVE debrief

Who should care

Linux kernel developers and maintainers should assess exposure and consider updating to resolve the issue. They should verify if their versions are affected and consider updating. This may involve reviewing the Linux kernel's source code, checking the version number, and consulting with the Linux kernel community for guidance. Security teams and operators may also be impacted as they need to ensure that their systems are updated and secure.

Why it matters

This vulnerability in the Linux kernel's iommufd may impact developers and maintainers who should verify if their versions are affected and consider updating.

• Verification of Linux kernel versions is required to determine exposure.
• Updating to a resolved version may be necessary to prevent reference leaks.
• Monitoring Linux kernel advisories is recommended for further information.

Technical summary

The Linux kernel's iommufd has a vulnerability where iommufd_access_notify_unmap() locks internal accesses before checking if they have an external unmap callback. This leads to a reference leak because the normal unmap path uses iommufd_put_object(). The issue arises from iommufd_access_notify_unmap() skipping internal accesses without an external unmap callback, but locking the object before checking if it's internal, leading to a reference leak. This vulnerability may impact Linux kernel developers and maintainers who should verify if their versions are affected and consider updating.

Defensive priority

Medium

Recommended defensive actions

• Verify if the Linux kernel version in use is affected by this vulnerability.
• Consider updating to a version of the Linux kernel where this issue is resolved.
• Monitor Linux kernel advisories for further information on this vulnerability.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in the Linux kernel's iommufd. However, the impact and affected versions require further verification from official Linux kernel sources. Linux kernel developers and maintainers should verify if their versions are affected and consider updating to resolve the issue. This may involve reviewing the Linux kernel's source code, checking the version number, and consulting with the Linux kernel community for guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.