Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72316dm era: fix NULL pointer dereference in metadata_open()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < a705e056c2f3dd067fb2ff414f0537530baa090b
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < bd5a80128bdfc93b1cae935a70da000b8c483e6e
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 17eb2ab13edd0b06ce6f996c5fd450d7efabb2e8
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 889374b8e4a60d13fe4a5a8ae3a311ca93d1a2c3
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 01c49eae7c6256f2d8cc08210a2bac3ee070e43a
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 14e03ecd3b1b5fc03c082b27a2f8889f8290c30e
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < b69ea153d30ce19ca8997eeeca1e2219fae5a29b
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 9ae672606c17891d90b282e3490b817620549599
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72316 badge
[![CVE-2026-72316](https://cveledger.app/badge/CVE-2026-72316.svg)](https://cveledger.app/cve/CVE-2026-72316)

Record last updated .