CVE-2026-89446 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, system administrators responsible for Linux kernel-based systems, and security teams should assess their exposure and take necessary actions. They should review Linux kernel versions for potential exposure, verify system configurations for iommufd usage, and monitor for updates from the Linux kernel community.

Why it matters

A vulnerability in the Linux kernel has been resolved, where the iommufd fails to release the current IOAS on xa_store() failure. This could potentially lead to resource leaks. Linux kernel developers and maintainers, as well as system administrators responsible for Linux kernel-based systems, should assess their exposure and take necessary actions.

• Potential resource leaks due to iommufd not releasing current IOAS on xa_store() failure
• Need to verify Linux kernel versions for potential exposure
• Need to monitor for updates from the Linux kernel community

Technical summary

The Linux kernel vulnerability is related to the iommufd not releasing the current IOAS on xa_store() failure. This could potentially lead to resource leaks. The iommufd_take_all_iova_rwsem() function takes an object reference and the iova_rwsem write lock before storing the IOAS in the temporary ioas_list xarray. If xa_store() fails, the current IOAS has not been inserted into ioas_list yet. iommufd_release_all_iova_rwsem() only unwinds IOAS objects already present in that xarray, so it cannot release the current IOAS.

Defensive priority

Medium

Recommended defensive actions

• Review Linux kernel versions for potential exposure
• Verify system configurations for iommufd usage
• Monitor for updates from the Linux kernel community
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• 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.

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further analysis is required to determine the full scope of the issue. The iommufd_take_all_iova_rwsem() function takes an object reference and the iova_rwsem write lock before storing the IOAS in the temporary ioas_list xarray. If xa_store() fails, the current IOAS has not been inserted into ioas_list yet.

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.