dax: read holder_ops once in dax_holder_notify_failure() (CVE-2026-93073) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93073

dax: read holder_ops once in dax_holder_notify_failure()

Answer in brief

CVE-2026-93073 records a Unknown severity vulnerability in dax: read holder_ops once in dax_holder_notify_failure(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=8012b866085523758780850087102421dbcce522 <1661b9bf78def01a8c96409569772d9b2592f4ba \|\| >=8012b866085523758780850087102421dbcce522 <0a42180d5410c98829ee72d1d426fb7faf9e6873 \|\| >=8012b866085523758780850087102421dbcce522 <ee1251621d1c7cf3155c6704542cbb358d799968 \|\| >=8012b866085523758780850087102421dbcce522 <6a37acecc7c29136235cbc446a1b89e81414344b \|\| >=8012b866085523758780850087102421dbcce522 <eb412f80311fc7ab6eb3203091a3fe59a5e9fd30 \|\| >=8012b866085523758780850087102421dbcce522 <7ae9d15bdcde0f2955ae13b6a95587f9e23b2359	1661b9bf78def01a8c96409569772d9b2592f4ba, 0a42180d5410c98829ee72d1d426fb7faf9e6873, ee1251621d1c7cf3155c6704542cbb358d799968, 6a37acecc7c29136235cbc446a1b89e81414344b, eb412f80311fc7ab6eb3203091a3fe59a5e9fd30, 7ae9d15bdcde0f2955ae13b6a95587f9e23b2359
Linux/Linuxgeneric	6.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1661b9bf78def01a8c96409569772d9b2592f4ba if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.