CVE-2026-72316: dm era: fix NULL pointer dereference in metadata_open()
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.22% (FIRST EPSS).
- Fixed version: Linux Linux 01c49eae7c6256f2d8cc08210a2bac3ee070e43a, 14e03ecd3b1b5fc03c082b27a2f8889f8290c30e, 17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8.
Low priority for now. Upgrade to Linux Linux 01c49eae7c6256f2d8cc08210a2bac3ee070e43a, 14e03ecd3b1b5fc03c082b27a2f8889f8290c30e, 17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8 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: dm era: fix NULL pointer dereference in metadata_open() metadata_open() returns NULL when kzalloc_obj() fails, but the caller era_ctr() only checks IS_ERR(md). Since IS_ERR(NULL) returns false, the NULL pointer is treated as a valid result and later assigned to era->md, leading to a NULL pointer dereference when the metadata is accessed. Fix this by returning ERR_PTR(-ENOMEM) on allocation failure, consistent with dm-cache-metadata.c, dm-thin-metadata.c, and dm-clone-metadata.c which all use ERR_PTR(-ENOMEM) for the same pattern.
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th 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.2%
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
- 3.15affected
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before a705e056c2f3dd067fb2ff414f0537530baa090baffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before bd5a80128bdfc93b1cae935a70da000b8c483e6eaffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 889374b8e4a60d13fe4a5a8ae3a311ca93d1a2c3affected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 01c49eae7c6256f2d8cc08210a2bac3ee070e43aaffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 14e03ecd3b1b5fc03c082b27a2f8889f8290c30eaffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before b69ea153d30ce19ca8997eeeca1e2219fae5a29baffected · git
- eec40579d84873dfb7021eb24c50360f073237c5 and later · before 9ae672606c17891d90b282e3490b817620549599affected · git
- before 3.15not 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-72314Aug 15, 2026 · regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK31Monitor
- ← EarlierCVE-2026-72315Aug 15, 2026 · smb: client: fix busy dentry warning on unmount after DIO31Monitor
- Later →CVE-2026-72317Aug 15, 2026 · SUNRPC: pin upper rpc_clnt across the TLS connect_worker39Monitor
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 | 01c49eae7c6256f2d8cc08210a2bac3ee070e43a | Vendor (CNA) |
| Linux Linux | 14e03ecd3b1b5fc03c082b27a2f8889f8290c30e | Vendor (CNA) |
| Linux Linux | 17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8 | Vendor (CNA) |
| Linux Linux | 889374b8e4a60d13fe4a5a8ae3a311ca93d1a2c3 | Vendor (CNA) |
| Linux Linux | 9ae672606c17891d90b282e3490b817620549599 | Vendor (CNA) |
| Linux Linux | a705e056c2f3dd067fb2ff414f0537530baa090b | Vendor (CNA) |
| Linux Linux | b69ea153d30ce19ca8997eeeca1e2219fae5a29b | Vendor (CNA) |
| Linux Linux | bd5a80128bdfc93b1cae935a70da000b8c483e6e | 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 (7 more)Show less
- git.kernel.org/stable/c/14e03ecd3b1b5fc03c082b27a2f8889f8290c30e
- git.kernel.org/stable/c/17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8
- git.kernel.org/stable/c/889374b8e4a60d13fe4a5a8ae3a311ca93d1a2c3
- git.kernel.org/stable/c/9ae672606c17891d90b282e3490b817620549599
- git.kernel.org/stable/c/a705e056c2f3dd067fb2ff414f0537530baa090b
- git.kernel.org/stable/c/b69ea153d30ce19ca8997eeeca1e2219fae5a29b
- git.kernel.org/stable/c/bd5a80128bdfc93b1cae935a70da000b8c483e6e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.