{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80973 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80973 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-80973 and fix it if it is affected.\n\nWhat it is: CVE-2026-80973 is a vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-80973 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-80973/ (Markdown: https://insights.sbomify.com/CVE-2026-80973/index.md)","id":"CVE-2026-80973","markdown":"https://insights.sbomify.com/CVE-2026-80973/index.md","name":"CVE-2026-80973","record":{"aliases":["AZL-100458","BELL-CVE-2026-80973","DEBIAN-CVE-2026-80973","GHSA-xqvm-46mc-2mf2","UBUNTU-CVE-2026-80973"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A malicious USB device can trigger an out-of-bounds read in the ALSA 6fire driver, leaking kernel memory to userspace via the MIDI input path.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","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\nALSA: 6fire: bound the MIDI event length from the device\n\nusb6fire_comm_receiver_handler() forwards a MIDI event using a length\nbyte the device supplies, with no bound and no check that the transfer\ndelivered that many bytes:\n\n\tif (!urb-\u003estatus) {\n\t\tif (rt-\u003ereceiver_buffer[0] == 0x10) /* midi in event */\n\t\t\tif (midi_rt)\n\t\t\t\tmidi_rt-\u003ein_received(midi_rt,\n\t\t\t\t\t\trt-\u003ereceiver_buffer + 2,\n\t\t\t\t\t\trt-\u003ereceiver_buffer[1]);\n\t}\n\nreceiver_buffer is a 64-byte kzalloc() buffer (COMM_RECEIVER_BUFSIZE), so\nonly 62 bytes follow the two-byte header.  receiver_buffer[1] is a u8 the\ndevice chooses, so a device that answers with 0x10 and a length of 0xFF\nmakes snd_rawmidi_receive() read 255 bytes starting two bytes into a\n64-byte object.  The bytes past the buffer are handed to userspace\nthrough the rawmidi read path.\n\nurb-\u003eactual_length is not consulted either, so a short transfer leaves\nboth the type byte and the length byte at their previous values and the\nhandler acts on stale data.\n\nThe receiver URB is submitted from usb6fire_comm_init() at probe, so the\nread happens on plug with no user action; forwarding to userspace also\nneeds a MIDI input substream open, since usb6fire_midi_in_received()\nonly calls snd_rawmidi_receive() when rt-\u003ein is set.\n\nKASAN on 7.2.0-rc5 (arm64), single packet from an emulated device:\n\n  BUG: KASAN: slab-out-of-bounds in snd_rawmidi_receive\n  Read of size 255 at addr ffff000009f64682 by task bash/183\n   __asan_memcpy\n   snd_rawmidi_receive\n   usb6fire_midi_in_received [snd_usb_6fire]\n   usb6fire_comm_receiver_handler [snd_usb_6fire]\n  Allocated by task 11:\n   usb6fire_comm_init [snd_usb_6fire]\n   usb6fire_chip_probe [snd_usb_6fire]\n  The buggy address is located 2 bytes inside of\n   allocated 64-byte region [ffff000009f64680, ffff000009f646c0)\n\nReject the event when the length exceeds the bytes that follow the\nheader, and require the transfer to have delivered the header plus that\nmany bytes.  The receiver URB is submitted with a 64-byte\ntransfer_buffer_length, so a genuine device cannot deliver an event\nlonger than those 62 bytes and nothing valid is dropped.\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: 6fire: bound the MIDI event length from the device","id":"CVE-2026-80973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"mfd: sm501: Fix potential memory leaks during remove","id":"CVE-2026-80974"},"packages":[],"prev":{"headline":"ALSA: aloop: Check card index validity at probe","id":"CVE-2026-80972"},"products":["Linux"],"published":"2026-09-11","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-19","vendors":["Linux"]},"summary":"A malicious USB device can trigger an out-of-bounds read in the ALSA 6fire driver, leaking kernel memory to userspace via the MIDI input path.","url":"https://insights.sbomify.com/CVE-2026-80973/"}