CVE-2026-74379: Linux kernel · dax/kmem: account for partial discontiguous resource upon removal
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ef4fc53898bd6c4d0119cc6d419ebef7f2560f31 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 18:03 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in ef4fc53898bd6c4d0119cc6d419ebef7f2560f31, d47b0b8a69a13e06afafa54723f3e8c99b0c788f, 799e54c510a03a65a57627018a817838d72f35bd +4
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented in the Linux kernel source code to skip non-existent resource ranges during dev_dax_kmem_remove(), preventing cleanup on NULL pointers. Users should update to the fixed kernel versions identified by the provided commit hashes to remediate this issue.
Description
A vulnerability in the Linux kernel's dax/kmem subsystem causes improper handling of partial resource allocation failures during device probing. Specifically, when dev_dax_kmem_probe() partially succeeds but fails to allocate some memory ranges, it returns success with some resources NULL. Later, dev_dax_kmem_remove() attempts to remove all ranges without checking if the resources exist, leading to cleanup on NULL pointers. This issue has been fixed by skipping non-existent ranges during removal.
References
- git.kernel.org/stable/c/ef4fc53898bd6c4d0119cc6d419ebef7f2560f31 (opens in a new tab)
- git.kernel.org/stable/c/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb (opens in a new tab)
- git.kernel.org/stable/c/d47b0b8a69a13e06afafa54723f3e8c99b0c788f (opens in a new tab)
- git.kernel.org/stable/c/799e54c510a03a65a57627018a817838d72f35bd (opens in a new tab)
- git.kernel.org/stable/c/598ed7393a639c7547b28ff3e14db9f1ac37c132 (opens in a new tab)
- git.kernel.org/stable/c/30ea97affbcce236c57287c82dc6ef7a29c63b76 (opens in a new tab)
- git.kernel.org/stable/c/8aa442cfce79e2d69e72fc8e0c0864ac2971149d (opens in a new tab)