In the Linux kernel, the following vulnerability has been resolved: iommufd: Release current IOAS on xa_store() failure… (CVE-2026-89446)
A vulnerability in the Linux kernel's iommufd component related to improper release of IOAS references on failure of xa_store() has been resolved. The issue occurs because the current IOAS is not released if xa_store() fails, potentially leading to resource management problems. The fix ensures that the current IOAS read-write semaphore and object reference are released properly before unwinding previously stored entries.
AI Analysis
Technical Summary
The Linux kernel's iommufd_take_all_iova_rwsem() function takes an object reference and a write lock before storing the IOAS in a temporary xarray. If the xa_store() call fails, the current IOAS is not yet inserted into the xarray, and the existing cleanup function iommufd_release_all_iova_rwsem() only releases IOAS objects already present in the xarray, thus missing the current IOAS. The vulnerability is fixed by releasing the current IOAS's read-write semaphore and object reference before unwinding previously stored entries, preventing resource leaks.
Potential Impact
The vulnerability could lead to improper release of kernel resources related to IOAS objects in the iommufd subsystem. This may cause resource leaks or inconsistent state within the kernel memory management for IO address spaces. No direct exploitation or broader impact details are provided.
Mitigation Recommendations
A fix has been applied to the Linux kernel to properly release the current IOAS on xa_store() failure. Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.
In the Linux kernel, the following vulnerability has been resolved: iommufd: Release current IOAS on xa_store() failure… (CVE-2026-89446)
Description
A vulnerability in the Linux kernel's iommufd component related to improper release of IOAS references on failure of xa_store() has been resolved. The issue occurs because the current IOAS is not released if xa_store() fails, potentially leading to resource management problems. The fix ensures that the current IOAS read-write semaphore and object reference are released properly before unwinding previously stored entries.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's iommufd_take_all_iova_rwsem() function takes an object reference and a write lock before storing the IOAS in a temporary xarray. If the xa_store() call fails, the current IOAS is not yet inserted into the xarray, and the existing cleanup function iommufd_release_all_iova_rwsem() only releases IOAS objects already present in the xarray, thus missing the current IOAS. The vulnerability is fixed by releasing the current IOAS's read-write semaphore and object reference before unwinding previously stored entries, preventing resource leaks.
Potential Impact
The vulnerability could lead to improper release of kernel resources related to IOAS objects in the iommufd subsystem. This may cause resource leaks or inconsistent state within the kernel memory management for IO address spaces. No direct exploitation or broader impact details are provided.
Mitigation Recommendations
A fix has been applied to the Linux kernel to properly release the current IOAS on xa_store() failure. Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9fjc-q922-2qfq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89446"]
Threat ID: 6aa4a02455bf5e2cf5a869b2
Added to database: 09/12/2026, 00:43:16 UTC
Last enriched: 09/12/2026, 01:17:19 UTC
Last updated: 09/12/2026, 01:17:19 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.