mtd: mtdswap: Avoid freeing registered blktrans device twice
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in ecadb9137aeaa0615183f8d23eabea2b45c862f1; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in eec130fc9ffbbd08a5d5432683122b79aca2a726; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in d5086911d532b82ca070d944aa08ddde00baefe4; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in a82d93fcfdfd26af17049c34319dfdd079cd1901; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in 5c349c533e72af2313c3be0f80a24d7407fa4777; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in 37be7bc2c2d09c18e939da20224405864a0090b9; From e8e3edb95ce6a146bc774b6cfad3553f4383edc8 · fixed in 779aa4c66a96bf43d2d62982ea1a9096a9128d87
- Linux Linux
4.14
- KernelLinux
From 4.14.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/ecadb9137aeaa0615183f8d23eabea2b45c862f1
- stable/c/eec130fc9ffbbd08a5d5432683122b79aca2a726
- stable/c/d5086911d532b82ca070d944aa08ddde00baefe4
- stable/c/0ce48c6ddea1a8e675a2eb0221b62a9950788f3c
- stable/c/a82d93fcfdfd26af17049c34319dfdd079cd1901
- stable/c/5c349c533e72af2313c3be0f80a24d7407fa4777
- stable/c/37be7bc2c2d09c18e939da20224405864a0090b9
- stable/c/779aa4c66a96bf43d2d62982ea1a9096a9128d87