Skip to main content
VulnerabilityPublished

CVE-2026-99038: Linux kernel · memstick: rtsx_usb_ms: complete requests after eject instead of dropping them

Source GCVE Database

0
Authoritative record:CVE-2026-99038· Medium

Not known to be exploited · fixed in f2c181e1d58e911804e14543b2f1cc6b23a0d4d6 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Medium

Rated by Threat Radar · 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 f2c181e1d58e911804e14543b2f1cc6b23a0d4d6, d7e811c3a49cd5cff529c157df886719e09370ec, c96ca94425b076dc398d929366e378d1e22ec794 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40, < f2c181e1d58e911804e14543b2f1cc6b23a0d4d6
Fixed in
  • f2c181e1d58e911804e14543b2f1cc6b23a0d4d6
LinuxLinuxAffected
  • ≥ 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40, < d7e811c3a49cd5cff529c157df886719e09370ec
Fixed in
  • d7e811c3a49cd5cff529c157df886719e09370ec
LinuxLinuxAffected
  • ≥ 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40, < c96ca94425b076dc398d929366e378d1e22ec794
Fixed in
  • c96ca94425b076dc398d929366e378d1e22ec794
LinuxLinuxAffected
  • ≥ 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40, < 5616da0f92339328fa1472876df51555e15ad340
Fixed in
  • 5616da0f92339328fa1472876df51555e15ad340
LinuxLinuxAffected
  • ≥ 99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40, < 5b599e28aeb3684772aef64f46cc6f25f4c67128
Fixed in
  • 5b599e28aeb3684772aef64f46cc6f25f4c67128
LinuxLinuxAffected
  • =3.16
Fixed in–

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.

References

Community reviews

Loading reviews…