Bug 2546524 (CVE-2026-98227) - CVE-2026-98227 kernel: memstick: ms_block: destroy io_queue workqueue on removal
Summary: CVE-2026-98227 kernel: memstick: ms_block: destroy io_queue workqueue on removal
Keywords:
Status: NEW
Alias: CVE-2026-98227
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-06 09:38 UTC by OSIDB Bzimport
Modified: 2026-10-09 06:01 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-06 09:38:47 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.