CVE-2026-93073 dax: read holder_ops once in dax_holder_notify_failure()
A race condition in the Linux kernel DAX subsystem can cause a null pointer dereference, leading to a system crash.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-93073?
CVE-2026-93073 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-93073?
How do I fix CVE-2026-93073?
Apply the vendor's patch.
Is CVE-2026-93073 being exploited?
There is no known exploitation of CVE-2026-93073 in the wild and no public exploit code.
Sources
Also known as AZL-102710, BELL-CVE-2026-93073, DEBIAN-CVE-2026-93073, GHSA-xxf3-2jmr-5rfc, UBUNTU-CVE-2026-93073.