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.
Affected versions
Linux kernel versions
3.12
and later are affected. Fixed in
6.1.189,
6.6.158,
6.12.112,
6.18.54,
7.2.8,
7.3-rc4
and their respective stable series.
References
6 totalFrequently asked questions
-
What is CVE-2026-98227?
CVE-2026-98227 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 3.12 onward and has been patched in 6.1.189, 6.6.158, 6.12.112 and others. CVE-2026-98227 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-98227?
Yes. CVE-2026-98227 has been patched. Fixed versions include 6.1.189, 6.6.158, 6.12.112 and others. If you are running Linux kernel 3.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-98227 actively exploited?
No. CVE-2026-98227 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.