Answer in brief
CVE-2026-99038 records a Unknown severity vulnerability in memstick: rtsx_usb_ms: complete requests after eject instead of dropping them. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 <f2c181e1d58e911804e14543b2f1cc6b23a0d4d6 || >=99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 <5b599e28aeb3684772aef64f46cc6f25f4c67128 || >=99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 <d7e811c3a49cd5cff529c157df886719e09370ec || >=99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 <5616da0f92339328fa1472876df51555e15ad340 || >=99451dceeb5fdd789f0a2eeb3ee029e80d2ccc40 <c96ca94425b076dc398d929366e378d1e22ec794 | f2c181e1d58e911804e14543b2f1cc6b23a0d4d6, 5b599e28aeb3684772aef64f46cc6f25f4c67128, d7e811c3a49cd5cff529c157df886719e09370ec, 5616da0f92339328fa1472876df51555e15ad340, c96ca94425b076dc398d929366e378d1e22ec794 |
| Linux/Linuxgeneric | 3.16 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.