GHSA-9FJC-Q922-2QFQ
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-89446"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:25Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: Release current IOAS on xa_store() failure\n\niommufd_take_all_iova_rwsem() takes an object reference and the\niova_rwsem write lock before storing the IOAS in the temporary ioas_list\nxarray.\n\nIf xa_store() fails, the current IOAS has not been inserted into\nioas_list yet. iommufd_release_all_iova_rwsem() only unwinds IOAS\nobjects already present in that xarray, so it cannot release the current\nIOAS.\n\nRelease the current IOAS rwsem and object reference before unwinding the\npreviously stored entries.",
"id": "GHSA-9fjc-q922-2qfq",
"modified": "2026-09-11T21:31:26Z",
"published": "2026-09-11T21:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89446"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/07b4fe1367f076886c1c47a19c70936138325087"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4ac2ce123824d5f885c868fa1f9f4d463141a2ba"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4c33d00ad9a911e87ea222986f732ce072e3aa26"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.