memstick: ms_block: destroy io_queue workqueue on removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 · < 90af7fde083e1b22c349c3a8b1626728e44e474c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's memstick ms_block driver fails to destroy a workqueue when a card is removed. Repeated card insert/remove cycles leak workqueues and kernel workers, potentially exhausting kernel memory. The described trigger requires card insertion and removal; the input does not specify authentication requirements.
Anyone running a Linux kernel with the memstick ms_block driver should check their kernel version; affected versions were not provided.