CVE-2026-93049

Unknown

Last modified

CVE-2026-93049 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < ecadb9137aeaa0615183f8d23eabea2b45c862f1; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < eec130fc9ffbbd08a5d5432683122b79aca2a726; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < d5086911d532b82ca070d944aa08ddde00baefe4; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < a82d93fcfdfd26af17049c34319dfdd079cd1901; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 5c349c533e72af2313c3be0f80a24d7407fa4777; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 37be7bc2c2d09c18e939da20224405864a0090b9; >= e8e3edb95ce6a146bc774b6cfad3553f4383edc8, < 779aa4c66a96bf43d2d62982ea1a9096a9128d87
LinuxLinux4.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93049?
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.
How severe is CVE-2026-93049?
Severity scoring for CVE-2026-93049 is pending analysis.
How do I fix CVE-2026-93049?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-93049?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST