CVE-2026-74379: dax/kmem: account for partial discontiguous resource upon removal
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 30ea97affbcce236c57287c82dc6ef7a29c63b76, 598ed7393a639c7547b28ff3e14db9f1ac37c132, 5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb.
Low priority for now. Upgrade to Linux Linux 30ea97affbcce236c57287c82dc6ef7a29c63b76, 598ed7393a639c7547b28ff3e14db9f1ac37c132, 5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dax/kmem: account for partial discontiguous resource upon removal When dev_dax_kmem_probe() partially succeeds (at least one range is mapped) but a subsequent range fails request_mem_region() or add_memory_driver_managed(), the probe silently continues, ultimately returning success, but with the corresponding range resource NULL'ed out. dev_dax_kmem_remove() iterates over all dax_device ranges regardless of if the underlying resource exists. When remove_memory() is called later, it returns 0 because the memory was never added which causes dev_dax_kmem_remove() to incorrectly assume the (nonexistent) resource can be removed and attempts cleanup on a NULL pointer. Fix this by skipping these ranges altogether, noting that these cases are considered success, such that the cleanup is still reached when all actually-added ranges are successfully removed.
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before ef4fc53898bd6c4d0119cc6d419ebef7f2560f31affected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before 5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bbaffected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before d47b0b8a69a13e06afafa54723f3e8c99b0c788faffected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before 799e54c510a03a65a57627018a817838d72f35bdaffected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before 598ed7393a639c7547b28ff3e14db9f1ac37c132affected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before 30ea97affbcce236c57287c82dc6ef7a29c63b76affected · git
- 60e93dc097f7f13a16a7e4b75b8803eb2adbb721 and later · before 8aa442cfce79e2d69e72fc8e0c0864ac2971149daffected · git
- before 5.10not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74377Aug 15, 2026 · RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path31Monitor
- ← EarlierCVE-2026-74378Aug 15, 2026 · RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe31Monitor
- Later →CVE-2026-74380Aug 15, 2026 · gpu: host1x: Fix iommu_map_sgtable() return value check35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 30ea97affbcce236c57287c82dc6ef7a29c63b76 | Vendor (CNA) |
| Linux Linux | 598ed7393a639c7547b28ff3e14db9f1ac37c132 | Vendor (CNA) |
| Linux Linux | 5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb | Vendor (CNA) |
| Linux Linux | 799e54c510a03a65a57627018a817838d72f35bd | Vendor (CNA) |
| Linux Linux | 8aa442cfce79e2d69e72fc8e0c0864ac2971149d | Vendor (CNA) |
| Linux Linux | d47b0b8a69a13e06afafa54723f3e8c99b0c788f | Vendor (CNA) |
| Linux Linux | ef4fc53898bd6c4d0119cc6d419ebef7f2560f31 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/598ed7393a639c7547b28ff3e14db9f1ac37c132
- git.kernel.org/stable/c/5d3139abb9d1671fa5e42c3d6d8cb3b05479c5bb
- git.kernel.org/stable/c/799e54c510a03a65a57627018a817838d72f35bd
- git.kernel.org/stable/c/8aa442cfce79e2d69e72fc8e0c0864ac2971149d
- git.kernel.org/stable/c/d47b0b8a69a13e06afafa54723f3e8c99b0c788f
- git.kernel.org/stable/c/ef4fc53898bd6c4d0119cc6d419ebef7f2560f31
Vendor advisories and official records. Exploit/PoC links are deliberately left out.