CVE-2026-98227
memstick: ms_block: destroy io_queue workqueue on removal
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 0ff795163f37109a134b5a421558530f8d091544Upgrade to: 0ff795163f37109a134b5a421558530f8d091544Affected: ≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 19c3da6621a253f1f8b937ed91bc22330a930d9cUpgrade to: 19c3da6621a253f1f8b937ed91bc22330a930d9cAffected: ≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 9a2e7cdc0880e735aff0968ee402f2c92a992b9bUpgrade to: 9a2e7cdc0880e735aff0968ee402f2c92a992b9bAffected: ≥ 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63, < 6611f78ec3fd4b33a00bfda20725b254a22979f6Upgrade to: 6611f78ec3fd4b33a00bfda20725b254a22979f6 + 2 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/0ff795163f37109a134b5a421558530f8d091544
- git.kernel.org/stable/c/19c3da6621a253f1f8b937ed91bc22330a930d9c
- git.kernel.org/stable/c/6611f78ec3fd4b33a00bfda20725b254a22979f6
And 3 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI