GHSA-8VMV-QF47-5PWF
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-13 09:32In the Linux kernel, the following vulnerability has been resolved:
rust: devres: fix race between concurrent revokers
There is a potential race condition when two paths try to revoke a Devres concurrently.
The driver core's devres_release_all() calls Revocable::revoke() via the release callback, while Devres::drop() calls revoke_nosync() on another CPU.
The revoker that does not claim the is_available swap returns immediately, but the revoker that did may still be executing drop_in_place() on the inner data. This can cause a use-after-free when the other revoker's caller proceeds to drop adjacent resources that drop_in_place() still references (e.g., Devres racing with SGTable freeing the backing sg_table and pages).
Fix this by adding a Completion. The release callback signals the Completion after revoke() finishes, and Devres::drop() waits for it when it loses the is_available swap. This ensures the wrapped object is fully torn down before Devres::drop() returns.
{
"affected": [],
"aliases": [
"CVE-2026-89764"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:20:07Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nrust: devres: fix race between concurrent revokers\n\nThere is a potential race condition when two paths try to revoke a\nDevres concurrently.\n\nThe driver core\u0027s devres_release_all() calls Revocable::revoke() via the\nrelease callback, while Devres::drop() calls revoke_nosync() on another\nCPU.\n\nThe revoker that does not claim the is_available swap returns\nimmediately, but the revoker that did may still be executing\ndrop_in_place() on the inner data. This can cause a use-after-free when\nthe other revoker\u0027s caller proceeds to drop adjacent resources that\ndrop_in_place() still references (e.g., Devres\u003cDmaMappedSgt\u003e racing with\nSGTable freeing the backing sg_table and pages).\n\nFix this by adding a Completion. The release callback signals the\nCompletion after revoke() finishes, and Devres::drop() waits for it when\nit loses the is_available swap. This ensures the wrapped object is fully\ntorn down before Devres::drop() returns.",
"id": "GHSA-8vmv-qf47-5pwf",
"modified": "2026-09-13T09:32:30Z",
"published": "2026-09-11T21:31:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89764"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/acc516dfa1972d31836b50abc0115216cd0fccc5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c7e3d57c705ab1053a6a1bbef96795e792da1540"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.