mtd: mtdoops: free page bitmap when the backing MTD is removed
- 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: mtdoops: free page bitmap when the backing MTD is removed mtdoops_notify_add() allocates oops_page_used when the configured MTD device is registered. mtdoops_notify_remove() detaches from that device but leaves the bitmap allocated. If the same MTD device is later registered again, the add path allocates a new bitmap and overwrites the old pointer, leaking one vmalloc allocation per remove/add cycle. This is only visible when the backing MTD device can disappear and be registered again while mtdoops remains loaded, so the usual static MTD case does not expose it. Free the bitmap after unregistering the dumper and flushing the pending workers, then clear the pointer and page count before a later attach can allocate fresh state. Clearing the pointer also keeps the module exit path from freeing the same bitmap a second time after a remove event.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in 477d61d54e097e90f748aa18d013805abd56bcbd; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in a91ac71e67c3e01ed9afd9841435bebb930293f8; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in 698944132083d143ef965c0090ee14ba1d9e1a5f; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in f25c804947e0a28c15e73da8e2e0db959cbed716; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in 8414f0e9f707226de20b48c7048179fd86d352fc; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in d06f91a52af11630c9f7e487f6daf242ac310cb8; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in 1e5cd8bc902331ff801df88cbb299029ae062753; From be95745f01677245a061a8f51473ef5ec8ad008e · fixed in 956e7da12c114f13c63d126ab1d79c3b6a819060
- Linux Linux
2.6.33
- KernelLinux
From 2.6.33 · 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.51; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/477d61d54e097e90f748aa18d013805abd56bcbd
- stable/c/a91ac71e67c3e01ed9afd9841435bebb930293f8
- stable/c/698944132083d143ef965c0090ee14ba1d9e1a5f
- stable/c/f25c804947e0a28c15e73da8e2e0db959cbed716
- stable/c/8414f0e9f707226de20b48c7048179fd86d352fc
- stable/c/d06f91a52af11630c9f7e487f6daf242ac310cb8
- stable/c/1e5cd8bc902331ff801df88cbb299029ae062753
- stable/c/956e7da12c114f13c63d126ab1d79c3b6a819060