CVE-2026-93073
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
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
- https://git.kernel.org/stable/c/ee1251621d1c7cf3155c6704542cbb358d799968
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.