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-89576dm-era: fix shadowed superblock leak on take-snap failure

Description

In the Linux kernel, the following vulnerability has been resolved: dm-era: fix shadowed superblock leak on take-snap failure metadata_take_snap() bumps the live superblock refcount and then dm_tm_shadow_block() allocates a new block for the metadata snapshot. If the subsequent dm_sm_inc_block() of writeset_tree_root or era_array_root fails, the function only unlocks the clone and returns. The newly allocated shadow block is never returned to the metadata space map, so each failed take-snap permanently leaks one metadata block. Free the clone with dm_sm_dec_block() on those error paths, matching the final step of metadata_drop_snap().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days 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 88% of all CVEs (13 Nov 2026)
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 – < 54dd21ca945ecc07885012b9f3e8197f091cfba0
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < ef00efb6fcaee88f50891279ceced17c614e97f7
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < e9fa68b89214bc65af0ef963af7ec3cce9f866e0
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < dc731d7fddfd6149f5e88ea080475d18c36d3c64
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < d66ceeefb87ddb097b0546bafc581380b816b048
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 36ff918637e3517f732188a3c39dbeae5b9cfb1b
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 6876ca330e741fb8886d12070cb6a7f9cb67257e
    • affected eec40579d84873dfb7021eb24c50360f073237c5 – < 39c5aa3bd8ec3912d2cd0b3fe092642b0d2b0713
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .