CVE-2026-93049

mtd: mtdswap: Avoid freeing registered blktrans device twice

N/A
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14e8e3edb95ce6a146bc774b6cfad3553f4383edc8
Vendor states this is fixed in 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c (fixed)
Vendor states this is fixed in 37be7bc2c2d09c18e939da20224405864a0090b9 (fixed)
Vendor states this is fixed in 5c349c533e72af2313c3be0f80a24d7407fa4777 (fixed)
Vendor states this is fixed in 779aa4c66a96bf43d2d62982ea1a9096a9128d87 (fixed)
Vendor states this is fixed in a82d93fcfdfd26af17049c34319dfdd079cd1901 (fixed)
Vendor states this is fixed in d5086911d532b82ca070d944aa08ddde00baefe4 (fixed)
Vendor states this is fixed in ecadb9137aeaa0615183f8d23eabea2b45c862f1 (fixed)
Vendor states this is fixed in eec130fc9ffbbd08a5d5432683122b79aca2a726 (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card