CVE-2026-98312: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-hgw4-f68w-cxg8
Share
Published
Advisory Summary

CVE-2026-98312 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98312 at a Glance

CVE Identifier CVE-2026-98312
GHSA Identifier GHSA-hgw4-f68w-cxg8
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98312

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98312, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: fix OOB write from device-reported iso length usb6fire_pcm_in_urb_handler() sizes each outgoing isochronous packet as (actual_length - 4) / (in_n_analog << 2) * (out_n_analog << 2) + 4, where actual_length is the unsigned length the device reported for the matching IN packet. A packet completed with status 0 and actual_length < 4 wraps the subtraction to 0x7fffffec; a zero-length isochronous packet is legal on the bus, and the preceding loop rejects only non-zero status. The sum reaches memset() on out_urb->buffer, a 4832-byte object from kcalloc(PCM_MAX_PACKET_SIZE, PCM_N_PACKETS_PER_URB). Even without the wrap the result is out of bounds: at 88.2/96 kHz the 4-in/6-out scaling turns a full 420-byte IN packet into 628, so eight packets span 5024 bytes of that buffer. usb_submit_urb() rejects an over-long descriptor only after the memset() and the usb6fire_pcm_playback() copy of user PCM data have run. Guard the subtraction as the sibling usb6fire_pcm_capture() already does, and limit the frame count to what fits in rt->out_packet_size, the OUT endpoint's wMaxPacketSize. This bounds total_length by the buffer size while keeping each packet length aligned to a whole output frame. BUG: KASAN: out-of-bounds in usb6fire_pcm_in_urb_handler (sound/usb/6fire/pcm.c:338) Write of size 18446744073709551456 at addr ffff88802a3d0000 by task vhci_rx/5018 Call Trace: dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) kasan_check_range (mm/kasan/generic.c:186 mm/kasan/generic.c:200) __asan_memset (mm/kasan/shadow.c:84) usb6fire_pcm_in_urb_handler (sound/usb/6fire/pcm.c:338) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1741) vhci_rx_loop (drivers/usb/usbip/vhci_rx.c:107 drivers/usb/usbip/vhci_rx.c:242) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) Allocated by task 10: __kmalloc_cache_noprof (mm/slub.c:5563) usb6fire_pcm_init (sound/usb/6fire/pcm.c:560 sound/usb/6fire/pcm.c:595) usb6fire_chip_probe (sound/usb/6fire/chip.c:133) usb_probe_interface (drivers/usb/core/driver.c:399) The buggy address belongs to the object at ffff88802a3d0000 which belongs to the cache kmalloc-8k of size 8192 The buggy address is located 0 bytes inside of 4832-byte region [ffff88802a3d0000, ffff88802a3d12e0) Kernel panic - not syncing: Fatal exception in interrupt

References

NVD — CVE-2026-98312 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98312
git.kernel.org/stable/c/001ba7c1d9... WEB
https://git.kernel.org/stable/c/001ba7c1d9677225a5ecbc3e60d4865c08bb21d8
git.kernel.org/stable/c/1589afe2d0... WEB
https://git.kernel.org/stable/c/1589afe2d099d3e817873bc474676968d7080410
git.kernel.org/stable/c/246de67755... WEB
https://git.kernel.org/stable/c/246de677552fe5dede293a1543b632e9853f31e4
git.kernel.org/stable/c/61e665fb48... WEB
https://git.kernel.org/stable/c/61e665fb48e9eee44ec6d610514af383b1802cc1
git.kernel.org/stable/c/cdc3153701... WEB
https://git.kernel.org/stable/c/cdc31537012bc7a58c95c6750db321b69dd802bb
git.kernel.org/stable/c/ea11ade105... WEB
https://git.kernel.org/stable/c/ea11ade10583cc45af515d6b24510dbfa0184ca6

Frequently Asked Questions

What is CVE-2026-98312?
CVE-2026-98312 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98312?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98312?
CVE-2026-98312 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98312?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hgw4-f68w-cxg8",
  "modified" : "2026-10-06T09:31:34Z",
  "published" : "2026-10-06T09:31:34Z",
  "aliases" : [ "CVE-2026-98312" ],
  "details" : "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 << 2) * (out_n_analog << 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 < 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->buffer, 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->out_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",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98312"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/001ba7c1d9677225a5ecbc3e60d4865c08bb21d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1589afe2d099d3e817873bc474676968d7080410"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/246de677552fe5dede293a1543b632e9853f31e4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/61e665fb48e9eee44ec6d610514af383b1802cc1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cdc31537012bc7a58c95c6750db321b69dd802bb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ea11ade10583cc45af515d6b24510dbfa0184ca6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-06T09:18:22Z"
  }
}