CVE-2026-99039

memstick: core: wait for request completion before freeing card

CVE-2026-99039 is fixed in 11 products on 1 platform, first by DEBIAN-CVE-2026-99039, released October 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.7
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0018
7th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
kernel-64kb · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-azure · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-default · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-default-base · sles 15.7 6.4.0-150700.53.90.1.150700.17.51.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-docs · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-livepatch-SLE15-SP7_Update_24 · sles 15.7 1-150700.15.3.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-obs-build · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-source · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-syms · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
kernel-zfcpdump · sles 15.7 6.4.0-150700.53.90.1 SUSE-SU-2026:5091-1 Nov 7, 2026
linux · Debian 13.5 (trixie) 6.12.113-1 DEBIAN-CVE-2026-99039 Oct 24, 2026
linux · Debian 14 7.2.11-1 DEBIAN-CVE-2026-99039 Oct 24, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.