memstick: core: wait for request completion before freeing card
Summary
| CVE | CVE-2026-99039 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-23 13:17:27 UTC |
| Updated | 2026-10-30 13:21:41 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: memstick: core: wait for request completion before freeing card In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete. The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card). However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write: BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990 Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239 Workqueue: events rtsx_usb_ms_handle_req Call Trace: ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450 rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline] rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396 worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560 kthread+0x373/0x450 kernel/kthread.c:436 Allocated by task 1662: memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline] memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396 Freed by task 1662: kfree+0x20c/0x650 mm/slub.c:6792 memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline] memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452 process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396 Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally. Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight. |
Risk And Classification
EPSS: 0.001770000 probability, percentile 0.072920000 (date 2026-11-01)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d b90f33ad9179c69658342323382bfed158f88cb9 git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d 1c23da6f148089d59b3d3e9b2e7f1eefa927cab9 git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d a2f1aa3341f185ca52103dc4908647570b208855 git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d c3ab92542475d59ae685cbb294e70ca4d0ba38e9 git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d 810580cf60edc75c9891c2de3225e4cda78e4d9f git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d f2795c50144d528dabc2cf2fd53c0f0c63a823a1 git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d 3af81770e2011c6ac7bb597a4af2e4f3591f928c git | Not specified |
| CNA | Linux | Linux | affected baf8532a147d5b76681ce040e2c8f25a3f0e718d aa0a37b5024d921e96ac4f8f487c8bfbf1f1a582 git | Not specified |
| CNA | Linux | Linux | affected 2.6.25 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.25 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.273 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.224 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.191 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.57 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.11 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/c3ab92542475d59ae685cbb294e70ca4d0ba38e9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/810580cf60edc75c9891c2de3225e4cda78e4d9f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3af81770e2011c6ac7bb597a4af2e4f3591f928c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a2f1aa3341f185ca52103dc4908647570b208855 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b90f33ad9179c69658342323382bfed158f88cb9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1c23da6f148089d59b3d3e9b2e7f1eefa927cab9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f2795c50144d528dabc2cf2fd53c0f0c63a823a1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/aa0a37b5024d921e96ac4f8f487c8bfbf1f1a582 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.