iommufd: Release current IOAS on xa_store() failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: iommufd: Release current IOAS on xa_store() failure iommufd_take_all_iova_rwsem() 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. Release the current IOAS rwsem and object reference before unwinding the previously stored entries.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 051ae5aa73d782a8be2699a11e17c68f28b4e758 · fixed in 4c33d00ad9a911e87ea222986f732ce072e3aa26; From 051ae5aa73d782a8be2699a11e17c68f28b4e758 · fixed in 07b4fe1367f076886c1c47a19c70936138325087; From 051ae5aa73d782a8be2699a11e17c68f28b4e758 · fixed in 4ac2ce123824d5f885c868fa1f9f4d463141a2ba
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4