CVE-2026-98227
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://git.kernel.org/stable/c/0ff795163f37109a134b5a421558530f8d091544
- https://git.kernel.org/stable/c/19c3da6621a253f1f8b937ed91bc22330a930d9c
- https://git.kernel.org/stable/c/6611f78ec3fd4b33a00bfda20725b254a22979f6
- https://git.kernel.org/stable/c/90af7fde083e1b22c349c3a8b1626728e44e474c
- https://git.kernel.org/stable/c/9a2e7cdc0880e735aff0968ee402f2c92a992b9b
- https://git.kernel.org/stable/c/f222bb8c30cf5699c560b29179ff2bddcac1f950
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.