CVE-2026-93073: Linux kernel · dax: read holder_ops once in dax_holder_notify_failure()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ee1251621d1c7cf3155c6704542cbb358d799968 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ee1251621d1c7cf3155c6704542cbb358d799968, eb412f80311fc7ab6eb3203091a3fe59a5e9fd30, 1661b9bf78def01a8c96409569772d9b2592f4ba +3
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In 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.
References
- git.kernel.org/stable/c/1661b9bf78def01a8c96409569772d9b2592f4ba (opens in a new tab)
- git.kernel.org/stable/c/0a42180d5410c98829ee72d1d426fb7faf9e6873 (opens in a new tab)
- git.kernel.org/stable/c/ee1251621d1c7cf3155c6704542cbb358d799968 (opens in a new tab)
- git.kernel.org/stable/c/6a37acecc7c29136235cbc446a1b89e81414344b (opens in a new tab)
- git.kernel.org/stable/c/eb412f80311fc7ab6eb3203091a3fe59a5e9fd30 (opens in a new tab)
- git.kernel.org/stable/c/7ae9d15bdcde0f2955ae13b6a95587f9e23b2359 (opens in a new tab)