CVE-2026-93073

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.

EPSS

0.2% chance of exploitation in the next 30 days; higher than 7% of CVEs (scores of 2026-10-25)

Published

2026-09-17

Modified

2026-10-19

Record from

the NVD, synced 2026-10-19

References

• https://git.kernel.org/stable/c/0a42180d5410c98829ee72d1d426fb7faf9e6873
• https://git.kernel.org/stable/c/1661b9bf78def01a8c96409569772d9b2592f4ba
• https://git.kernel.org/stable/c/6a37acecc7c29136235cbc446a1b89e81414344b
• https://git.kernel.org/stable/c/7ae9d15bdcde0f2955ae13b6a95587f9e23b2359
• https://git.kernel.org/stable/c/eb412f80311fc7ab6eb3203091a3fe59a5e9fd30

Check your stackJSON