{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99039 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99039 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99039 and fix it if it is affected.\n\nWhat it is: CVE-2026-99039 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99039 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99039/ (Markdown: https://insights.sbomify.com/CVE-2026-99039/index.md)","id":"CVE-2026-99039","markdown":"https://insights.sbomify.com/CVE-2026-99039/index.md","name":"CVE-2026-99039","record":{"aliases":["AZL-110912","BELL-CVE-2026-99039","DEBIAN-CVE-2026-99039","GHSA-r8cv-6pg4-74wg","UBUNTU-CVE-2026-99039"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemstick: core: wait for request completion before freeing card\n\nIn memstick_alloc_card() and memstick_set_rw_addr(),\nwait_for_completion_timeout() is used to wait for device identification\nand address configuration requests to complete.\n\nThe memstick subsystem does not provide an abort or cancellation\ncallback in struct memstick_host for in-flight requests. If\nwait_for_completion_timeout() expires (for instance, when a USB transfer\nor command retry is delayed), memstick_alloc_card() returns an error and\nfrees the memstick_dev structure via kfree(card).\n\nHowever, the host controller driver (such as rtsx_usb_ms) is still\nrunning the request asynchronously in worker context. When the transfer\neventually finishes, the driver writes into host-\u003ereq-\u003edata, which\npoints to memory inside the already freed card structure. This leads to\na KASAN slab-use-after-free write:\n\n  BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990\n  Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239\n  Workqueue: events rtsx_usb_ms_handle_req\n  Call Trace:\n   ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450\n   rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]\n   rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531\n   process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396\n   worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560\n   kthread+0x373/0x450 kernel/kthread.c:436\n\n  Allocated by task 1662:\n   memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]\n   memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452\n   process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396\n\n  Freed by task 1662:\n   kfree+0x20c/0x650 mm/slub.c:6792\n   memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]\n   memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452\n   process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396\n\nHost controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already\nimplement their own hardware and bus timeouts, and callers in\nmspro_block and ms_block already rely on wait_for_completion()\nunconditionally.\n\nReplace wait_for_completion_timeout() with wait_for_completion() in\nmemstick_set_rw_addr() and memstick_alloc_card() so that the card\nstructure is never freed while an asynchronous request is in flight.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"memstick: core: wait for request completion before freeing card","id":"CVE-2026-99039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"KEYS: Fix add_key() race with keyring restriction","id":"CVE-2026-99040"},"packages":[],"prev":{"headline":"memstick: rtsx_usb_ms: complete requests after eject instead of dropping them","id":"CVE-2026-99038"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99039/"}