{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99038 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99038 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99038 and fix it if it is affected.\n\nWhat it is: CVE-2026-99038 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99038 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-99038/ (Markdown: https://insights.sbomify.com/CVE-2026-99038/index.md)","id":"CVE-2026-99038","markdown":"https://insights.sbomify.com/CVE-2026-99038/index.md","name":"CVE-2026-99038","record":{"aliases":["AZL-110909","BELL-CVE-2026-99038","DEBIAN-CVE-2026-99038","GHSA-95v5-2rxr-2qx7","UBUNTU-CVE-2026-99038"],"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: rtsx_usb_ms: complete requests after eject instead of dropping them\n\nmemstick_check() can pass its host-\u003eremoving check just before\nrtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then\nsilently dropped: rtsx_usb_ms_request() skips schedule_work() once eject\nis set, and drv_remove's cancel_work_sync() can also cancel a queued\nhandle_req before it picks the request up. Nobody completes\ncard-\u003emrq_complete.\n\nOnce memstick core waits for requests without a timeout (\"memstick: core:\nwait for request completion before freeing card\"), this hangs removal:\nmemstick_check() never returns and memstick_remove_host() blocks in\nflush_workqueue():\n\n  INFO: task kworker/u10:3:65 blocked for more than 20 seconds.\n  Workqueue: kmemstick memstick_check\n   __wait_for_common\n   memstick_check\n\n  INFO: task kworker/1:1:33 blocked for more than 20 seconds.\n  Workqueue: usb_hub_wq hub_event\n   __flush_workqueue\n   memstick_remove_host\n   rtsx_usb_ms_drv_remove\n\nNever drop a request. rtsx_usb_ms_request() always schedules handle_req,\nand handle_req fails requests with -ENOMEDIUM once eject is set, without\ntouching the device. drv_remove flushes handle_req instead of cancelling\nit, and cancels it only after memstick_remove_host(), when no new\nrequest can arrive, so it cannot run on a freed host.\n\nThe host_mutex drain in drv_remove is removed: handle_req always leaves\nhost-\u003ereq NULL when it finishes, so the drain never had anything to do,\nand it would now race with handle_req.","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: rtsx_usb_ms: complete requests after eject instead of dropping them","id":"CVE-2026-99038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"memstick: core: wait for request completion before freeing card","id":"CVE-2026-99039"},"packages":[],"prev":{"headline":"dm-crypt: reject the lmk IV mode with AEAD ciphers","id":"CVE-2026-99037"},"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-99038/"}