{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80971 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80971 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80971 and fix it if it is affected.\n\nWhat it is: CVE-2026-80971 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80971 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-80971/ (Markdown: https://insights.sbomify.com/CVE-2026-80971/index.md)","id":"CVE-2026-80971","markdown":"https://insights.sbomify.com/CVE-2026-80971/index.md","name":"CVE-2026-80971","record":{"aliases":["AZL-100503","BELL-CVE-2026-80971","DEBIAN-CVE-2026-80971","GHSA-27wq-xjr3-w8c9","UBUNTU-CVE-2026-80971"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the ALSA bcd2000 driver allows attackers to cause memory corruption or system crashes via race conditions during device disconnection.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: bcd2000: clear the URB pointers on disconnect\n\nbcd2000_free_usb_related_resources() frees both URBs and leaves the\npointers behind:\n\n\tusb_kill_urb(bcd2k-\u003emidi_out_urb);\n\tusb_kill_urb(bcd2k-\u003emidi_in_urb);\n\n\tusb_free_urb(bcd2k-\u003emidi_out_urb);\n\tusb_free_urb(bcd2k-\u003emidi_in_urb);\n\nThe rawmidi device outlives that call.  A substream that is still open\nwhen the device is unplugged reaches bcd2000_midi_send() from the\ntrigger path on close.  That function writes to the freed URB and then\nhands it to the USB core:\n\n\tbcd2k-\u003emidi_out_urb-\u003etransfer_buffer_length = BUFSIZE;\n\t...\n\tret = usb_submit_urb(bcd2k-\u003emidi_out_urb, GFP_ATOMIC);\n\nusb_kill_urb() does not stop a later submission either, so a submit that\nraces the disconnect can requeue the URB after it has been reaped.\nmidi_in_urb is exposed the same way: bcd2000_input_complete() resubmits\nit from the completion handler.\n\nKASAN on 7.2.0-rc5 (arm64):\n\n  BUG: KASAN: slab-use-after-free in bcd2000_midi_send [snd_bcd2000]\n  Write of size 4 at addr ffff00001827d388 by task bpoc/168\n   __asan_store4\n   bcd2000_midi_send [snd_bcd2000]\n   bcd2000_midi_output_trigger [snd_bcd2000]\n   snd_rawmidi_kernel_write1\n   close_substream.part.0\n  Freed by task 168:\n   usb_free_urb\n   bcd2000_disconnect [snd_bcd2000]\n\n  BUG: KASAN: slab-use-after-free in usb_submit_urb\n  Read of size 8 at addr ffff00001827d3b8 by task bpoc/168\n\nClear both pointers after freeing and test them on the paths that can\nstill run.  Poison the URBs before freeing them: usb_poison_urb() waits\nfor a running completion handler and rejects any later submission, so\nafter it returns the input path is quiesced and only the rawmidi trigger\npath can still reach bcd2000_midi_send().  No unpoison is needed; the\nURBs are freed on the next line.\n\nDiscovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e","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":"ALSA: bcd2000: clear the URB pointers on disconnect","id":"CVE-2026-80971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ALSA: aloop: Check card index validity at probe","id":"CVE-2026-80972"},"packages":[],"prev":{"headline":"ALSA: FCP: do not copy out an uninitialised init response","id":"CVE-2026-80970"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the ALSA bcd2000 driver allows attackers to cause memory corruption or system crashes via race conditions during device disconnection.","url":"https://insights.sbomify.com/CVE-2026-80971/"}