CVE Catalog

CVE-2026-90278

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the md subsystem's __md_stop() destroyed the bitmap before calling mddev_detach(), causing mddev_detach() to skip bitmap_ops->wait_behind_writes(). With llbitmap, RAID1 behind-write completions could then run after llbitmap storage had been freed. The fix calls mddev_detach() before md_bitmap_destroy().

Risk Assessment

Can lead to use-after-free and kernel instability, potentially causing system crashes or data corruption on RAID1 arrays using llbitmap. Occurs during array teardown.

Recommendation

Update the Linux kernel to a version containing the fix that reorders mddev_detach() and md_bitmap_destroy(). Schedule the update before routinely stopping RAID1 arrays.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: md: wait for behind writes before destroying bitmap __md_stop() destroyed the bitmap before calling mddev_detach(). That made mddev_detach() skip bitmap_ops->wait_behind_writes(), because the bitmap was already disconnected from mddev. This was still safe for the legacy bitmap because bitmap_destroy() waits for behind writes itself. llbitmap keeps that wait in its ->wait_behind_writes() operation instead, while ->destroy() tears down the llbitmap storage. With the old ordering, RAID1 behind-write completions could still run after llbitmap storage had been freed. Call mddev_detach() before md_bitmap_destroy() so the common detach path can wait for behind writes while the bitmap is still alive. Only destroy the bitmap after those users are gone.

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