CVE Catalog

CVE-2026-89953

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, mtdoops_notify_add() allocates the oops_page_used bitmap when the configured MTD device is registered, but mtdoops_notify_remove() leaves it allocated. Re-registering the same MTD device leaks one vmalloc allocation per remove/add cycle.

Risk Assessment

Repeated remove/re-register cycles of the MTD device lead to a kernel memory leak, which can eventually exhaust resources and affect system stability.

Recommendation

Update the Linux kernel to a version containing the fix that frees the bitmap after unregistering the dumper and flushing pending workers, and clears the pointer and page count.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS