CVE-2026-89953

mtd: mtdoops: free page bitmap when the backing MTD is removed

N/A
Published: September 16, 2026 at 10:32 AM UTC
Updated: October 19, 2026 at 09:18 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: 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.

Affected

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

2.6.33be95745f01677245a061a8f51473ef5ec8ad008e
Vendor states this is fixed in 1e5cd8bc902331ff801df88cbb299029ae062753 (fixed)
Vendor states this is fixed in 477d61d54e097e90f748aa18d013805abd56bcbd (fixed)
Vendor states this is fixed in 698944132083d143ef965c0090ee14ba1d9e1a5f (fixed)
Vendor states this is fixed in 8414f0e9f707226de20b48c7048179fd86d352fc (fixed)
Vendor states this is fixed in 956e7da12c114f13c63d126ab1d79c3b6a819060 (fixed)
Vendor states this is fixed in a91ac71e67c3e01ed9afd9841435bebb930293f8 (fixed)
Vendor states this is fixed in d06f91a52af11630c9f7e487f6daf242ac310cb8 (fixed)
Vendor states this is fixed in f25c804947e0a28c15e73da8e2e0db959cbed716 (fixed)
Vendor states this is fixed in 2.6.33 (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.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (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