GHSA-XXF3-2JMR-5RFC
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
dax: read holder_ops once in dax_holder_notify_failure()
dax_holder_notify_failure() reads dax_dev->holder_ops twice without READ_ONCE() -- once for the NULL check and once for the indirect notify_failure() call. A concurrent fs_put_dax() can clear holder_ops between the two reads, so the check can observe a non-NULL pointer while the call dereferences NULL. (kill_dax() also clears holder_ops, but only after synchronize_srcu(), so it cannot race a reader that is inside dax_read_lock(); fs_put_dax() does no such synchronization.)
Fetch holder_ops once into a local with READ_ONCE() so the NULL check and the indirect call observe the same value.
{
"affected": [],
"aliases": [
"CVE-2026-93073"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:18:01Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndax: read holder_ops once in dax_holder_notify_failure()\n\ndax_holder_notify_failure() reads dax_dev-\u003eholder_ops twice without\nREAD_ONCE() -- once for the NULL check and once for the indirect\nnotify_failure() call. A concurrent fs_put_dax() can clear holder_ops\nbetween the two reads, so the check can observe a non-NULL pointer while\nthe call dereferences NULL. (kill_dax() also clears holder_ops, but only\nafter synchronize_srcu(), so it cannot race a reader that is inside\ndax_read_lock(); fs_put_dax() does no such synchronization.)\n\nFetch holder_ops once into a local with READ_ONCE() so the NULL check and\nthe indirect call observe the same value.",
"id": "GHSA-xxf3-2jmr-5rfc",
"modified": "2026-09-17T18:32:09Z",
"published": "2026-09-17T18:32:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93073"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0a42180d5410c98829ee72d1d426fb7faf9e6873"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1661b9bf78def01a8c96409569772d9b2592f4ba"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6a37acecc7c29136235cbc446a1b89e81414344b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7ae9d15bdcde0f2955ae13b6a95587f9e23b2359"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/eb412f80311fc7ab6eb3203091a3fe59a5e9fd30"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee1251621d1c7cf3155c6704542cbb358d799968"
}
],
"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.