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-99038memstick: rtsx_usb_ms: complete requests after eject instead of dropping them

Description

In the Linux kernel, the following vulnerability has been resolved: memstick: rtsx_usb_ms: complete requests after eject instead of dropping them memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete. Once memstick core waits for requests without a timeout ("memstick: core: wait for request completion before freeing card"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue(): INFO: task kworker/u10:3:65 blocked for more than 20 seconds. Workqueue: kmemstick memstick_check __wait_for_common memstick_check INFO: task kworker/1:1:33 blocked for more than 20 seconds. Workqueue: usb_hub_wq hub_event __flush_workqueue memstick_remove_host rtsx_usb_ms_drv_remove Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host. The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 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.18% · top 93% of all CVEs (18 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 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < c48245ef696e590e92cbfb622625642bec8dbbad
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < 602a00d75d2ab079c9ab7c0d7b56ae436e604148
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < 8e4eda6e1b00624820fea1d35508d7422330ee25
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < f2c181e1d58e911804e14543b2f1cc6b23a0d4d6
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < 5b599e28aeb3684772aef64f46cc6f25f4c67128
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < d7e811c3a49cd5cff529c157df886719e09370ec
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < 5616da0f92339328fa1472876df51555e15ad340
    • affected 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 – < c96ca94425b076dc398d929366e378d1e22ec794
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .