Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98227memstick: ms_block: destroy io_queue workqueue on removal

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 0ff795163f37109a134b5a421558530f8d091544
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 19c3da6621a253f1f8b937ed91bc22330a930d9c
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 9a2e7cdc0880e735aff0968ee402f2c92a992b9b
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 6611f78ec3fd4b33a00bfda20725b254a22979f6
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < f222bb8c30cf5699c560b29179ff2bddcac1f950
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 90af7fde083e1b22c349c3a8b1626728e44e474c
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98227 badge
[![CVE-2026-98227](https://cveledger.app/badge/CVE-2026-98227.svg)](https://cveledger.app/cve/CVE-2026-98227)

Record last updated .