CVE-2026-98227: Linux kernel · memstick: ms_block: destroy io_queue workqueue on removal
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f222bb8c30cf5699c560b29179ff2bddcac1f950 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:30 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f222bb8c30cf5699c560b29179ff2bddcac1f950, 6611f78ec3fd4b33a00bfda20725b254a22979f6, 90af7fde083e1b22c349c3a8b1626728e44e474c +3
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel as indicated by the fixed commit versions. Users should update to a kernel version that includes these fixes to resolve the memory leak issue.
Description
A memory leak vulnerability exists in the Linux kernel's memstick driver due to the io_queue workqueue not being destroyed on card removal. This causes kernel memory exhaustion over repeated card insert/remove cycles. The issue is fixed by destroying the workqueue in the msb_remove() function after the disk removal and queue draining.
References
- git.kernel.org/stable/c/0ff795163f37109a134b5a421558530f8d091544 (opens in a new tab)
- git.kernel.org/stable/c/19c3da6621a253f1f8b937ed91bc22330a930d9c (opens in a new tab)
- git.kernel.org/stable/c/9a2e7cdc0880e735aff0968ee402f2c92a992b9b (opens in a new tab)
- git.kernel.org/stable/c/6611f78ec3fd4b33a00bfda20725b254a22979f6 (opens in a new tab)
- git.kernel.org/stable/c/f222bb8c30cf5699c560b29179ff2bddcac1f950 (opens in a new tab)
- git.kernel.org/stable/c/90af7fde083e1b22c349c3a8b1626728e44e474c (opens in a new tab)