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-93049

mtd: mtdswap: Avoid freeing registered blktrans device twice

Description

In the Linux kernel, the following vulnerability has been resolved: mtd: mtdswap: Avoid freeing registered blktrans device twice In mtdswap_add_mtd(), debugfs setup failure after successful blktrans registration can free mbd_dev twice. add_mtd_blktrans_dev() initializes the blktrans device reference and publishes the disk. Once that succeeds, del_mtd_blktrans_dev() tears the disk down and drops the blktrans reference; when that reference reaches zero, blktrans_dev_release() frees the mtd_blktrans_dev. The debugfs failure path called del_mtd_blktrans_dev(mbd_dev), then fell through the common cleanup label and called kfree(mbd_dev) again. Clear the local pointer after deregistration so the common cleanup can still release the mtdswap state without freeing the blktrans object twice. This issue was found by a static analysis checker and confirmed by manual source review.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 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 (12 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 e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < ecadb9137aeaa0615183f8d23eabea2b45c862f1
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < eec130fc9ffbbd08a5d5432683122b79aca2a726
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < d5086911d532b82ca070d944aa08ddde00baefe4
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < a82d93fcfdfd26af17049c34319dfdd079cd1901
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < 5c349c533e72af2313c3be0f80a24d7407fa4777
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < 37be7bc2c2d09c18e939da20224405864a0090b9
    • affected e8e3edb95ce6a146bc774b6cfad3553f4383edc8 – < 779aa4c66a96bf43d2d62982ea1a9096a9128d87
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • 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.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 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-93049 badge
[![CVE-2026-93049](https://cveledger.app/badge/CVE-2026-93049.svg)](https://cveledger.app/cve/CVE-2026-93049)

Record last updated .