{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98312 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98312 is a vulnerability in Linux, published on 6 Oct 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-98312 and fix it if it is affected.\n\nWhat it is: CVE-2026-98312 is a vulnerability in Linux, published on 6 Oct 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-98312 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-98312/ (Markdown: https://insights.sbomify.com/CVE-2026-98312/index.md)","id":"CVE-2026-98312","markdown":"https://insights.sbomify.com/CVE-2026-98312/index.md","name":"CVE-2026-98312","record":{"aliases":["AZL-106407","BELL-CVE-2026-98312","DEBIAN-CVE-2026-98312","GHSA-hgw4-f68w-cxg8","UBUNTU-CVE-2026-98312"],"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":"none","summary":"A malicious USB device can trigger an integer overflow leading to an out-of-bounds write in the ALSA 6fire driver, potentially causing code execution or system crash.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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: fix OOB write from device-reported iso length\n\nusb6fire_pcm_in_urb_handler() sizes each outgoing isochronous packet as\n(actual_length - 4) / (in_n_analog \u003c\u003c 2) * (out_n_analog \u003c\u003c 2) + 4, where\nactual_length is the unsigned length the device reported for the matching\nIN packet.  A packet completed with status 0 and actual_length \u003c 4 wraps\nthe subtraction to 0x7fffffec; a zero-length isochronous packet is legal\non the bus, and the preceding loop rejects only non-zero status.  The sum\nreaches memset() on out_urb-\u003ebuffer, a 4832-byte object from\nkcalloc(PCM_MAX_PACKET_SIZE, PCM_N_PACKETS_PER_URB).\n\nEven without the wrap the result is out of bounds: at 88.2/96 kHz the\n4-in/6-out scaling turns a full 420-byte IN packet into 628, so eight\npackets span 5024 bytes of that buffer.  usb_submit_urb() rejects an\nover-long descriptor only after the memset() and the\nusb6fire_pcm_playback() copy of user PCM data have run.\n\nGuard the subtraction as the sibling usb6fire_pcm_capture() already does,\nand limit the frame count to what fits in rt-\u003eout_packet_size, the OUT\nendpoint's wMaxPacketSize.  This bounds total_length by the buffer size\nwhile keeping each packet length aligned to a whole output frame.\n\n  BUG: KASAN: out-of-bounds in usb6fire_pcm_in_urb_handler (sound/usb/6fire/pcm.c:338)\n  Write of size 18446744073709551456 at addr ffff88802a3d0000 by task vhci_rx/5018\n  Call Trace:\n   dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)\n   print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)\n   kasan_report (mm/kasan/report.c:595)\n   kasan_check_range (mm/kasan/generic.c:186 mm/kasan/generic.c:200)\n   __asan_memset (mm/kasan/shadow.c:84)\n   usb6fire_pcm_in_urb_handler (sound/usb/6fire/pcm.c:338)\n   __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657)\n   usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1741)\n   vhci_rx_loop (drivers/usb/usbip/vhci_rx.c:107 drivers/usb/usbip/vhci_rx.c:242)\n   kthread (kernel/kthread.c:436)\n   ret_from_fork (arch/x86/kernel/process.c:158)\n   ret_from_fork_asm (arch/x86/entry/entry_64.S:245)\n\n  Allocated by task 10:\n   __kmalloc_cache_noprof (mm/slub.c:5563)\n   usb6fire_pcm_init (sound/usb/6fire/pcm.c:560 sound/usb/6fire/pcm.c:595)\n   usb6fire_chip_probe (sound/usb/6fire/chip.c:133)\n   usb_probe_interface (drivers/usb/core/driver.c:399)\n\n  The buggy address belongs to the object at ffff88802a3d0000\n   which belongs to the cache kmalloc-8k of size 8192\n  The buggy address is located 0 bytes inside of\n   4832-byte region [ffff88802a3d0000, ffff88802a3d12e0)\n  Kernel panic - not syncing: Fatal exception in interrupt","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: fix OOB write from device-reported iso length","id":"CVE-2026-98312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"drm/msm/dp: skip PUSH_IDLE when the link was never enabled","id":"CVE-2026-98313"},"packages":[],"prev":{"headline":"wifi: virt_wifi: don't transfer operstate before register","id":"CVE-2026-98311"},"products":["Linux"],"published":"2026-10-06","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 integer overflow leading to an out-of-bounds write in the ALSA 6fire driver, potentially causing code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-98312/"}