CVE-2026-98227

Unknown

Last modified

CVE-2026-98227 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: memstick: ms_block: destroy io_queue workqueue on removal msb_init_disk() creates the per-card ordered workqueue msb->io_queue with alloc_ordered_workqueue(). It is torn down with destroy_workqueue() only on the init error path; msb_remove() never destroys it.

Description

In the Linux kernel, the following vulnerability has been resolved: memstick: ms_block: destroy io_queue workqueue on removal msb_init_disk() creates the per-card ordered workqueue msb->io_queue with alloc_ordered_workqueue(). It is torn down with destroy_workqueue() only on the init error path; msb_remove() never destroys it. msb_stop() merely flushes the queue, and neither msb_data_clear() nor put_disk() free it. As a result every card insert/remove cycle leaks the workqueue and its kworker, exhausting kernel memory over repeated cycles. Destroy the workqueue in msb_remove() after the disk has been removed and the queue drained.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 0ff795163f37109a134b5a421558530f8d091544; >= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 19c3da6621a253f1f8b937ed91bc22330a930d9c; >= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 9a2e7cdc0880e735aff0968ee402f2c92a992b9b; >= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 6611f78ec3fd4b33a00bfda20725b254a22979f6; >= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < f222bb8c30cf5699c560b29179ff2bddcac1f950; >= 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 90af7fde083e1b22c349c3a8b1626728e44e474c
LinuxLinux3.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98227?
In the Linux kernel, the following vulnerability has been resolved: memstick: ms_block: destroy io_queue workqueue on removal msb_init_disk() creates the per-card ordered workqueue msb->io_queue with alloc_ordered_workqueue(). It is torn down with destroy_workqueue() only on the init error path; msb_remove() never destroys it. msb_stop() merely flushes the queue, and neither msb_data_clear() nor put_disk() free it. As a result every card insert/remove cycle leaks the workqueue and its kworker, exhausting kernel memory over repeated cycles. Destroy the workqueue in msb_remove() after the disk has been removed and the queue drained.
How severe is CVE-2026-98227?
Severity scoring for CVE-2026-98227 is pending analysis.
How do I fix CVE-2026-98227?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98227?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST