Skip to main content
VulnerabilityPublished Updated

CVE-2026-93049: Linux kernel · mtd: mtdswap: Avoid freeing registered blktrans device twice

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in eec130fc9ffbbd08a5d5432683122b79aca2a726 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in eec130fc9ffbbd08a5d5432683122b79aca2a726, ecadb9137aeaa0615183f8d23eabea2b45c862f1, d5086911d532b82ca070d944aa08ddde00baefe4 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < eec130fc9ffbbd08a5d5432683122b79aca2a726
Fixed in
  • eec130fc9ffbbd08a5d5432683122b79aca2a726
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < ecadb9137aeaa0615183f8d23eabea2b45c862f1
Fixed in
  • ecadb9137aeaa0615183f8d23eabea2b45c862f1
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < d5086911d532b82ca070d944aa08ddde00baefe4
Fixed in
  • d5086911d532b82ca070d944aa08ddde00baefe4
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < a82d93fcfdfd26af17049c34319dfdd079cd1901
Fixed in
  • a82d93fcfdfd26af17049c34319dfdd079cd1901
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 779aa4c66a96bf43d2d62982ea1a9096a9128d87
Fixed in
  • 779aa4c66a96bf43d2d62982ea1a9096a9128d87
LinuxLinuxAffected
  • ≥ e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 37be7bc2c2d09c18e939da20224405864a0090b9
Fixed in
  • 37be7bc2c2d09c18e939da20224405864a0090b9

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.

References

Community reviews

Loading reviews…