Strix
63.5K

CVE-2026-93073

Unknown

Last modified

CVE-2026-93073 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8012b866085523758780850087102421dbcce522, < 1661b9bf78def01a8c96409569772d9b2592f4ba; >= 8012b866085523758780850087102421dbcce522, < 0a42180d5410c98829ee72d1d426fb7faf9e6873; >= 8012b866085523758780850087102421dbcce522, < ee1251621d1c7cf3155c6704542cbb358d799968; >= 8012b866085523758780850087102421dbcce522, < 6a37acecc7c29136235cbc446a1b89e81414344b; >= 8012b866085523758780850087102421dbcce522, < eb412f80311fc7ab6eb3203091a3fe59a5e9fd30; >= 8012b866085523758780850087102421dbcce522, < 7ae9d15bdcde0f2955ae13b6a95587f9e23b2359
LinuxLinux6.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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.
How severe is CVE-2026-93073?
Severity scoring for CVE-2026-93073 is pending analysis.
How do I fix CVE-2026-93073?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93073?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST