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.
Fix
Microsoft's update · Moderate
- Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.158.1-1
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-30.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusReceived → PublishedNVD modified 2026-10-19 09:15
- First seenunscoredNVD modified 2026-10-19 10:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- 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