CVE-2026-98265: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98265 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-98265 at a Glance
How to Fix CVE-2026-98265
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.
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-98265, 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
References
Frequently Asked Questions
What is CVE-2026-98265?
Which Software versions are affected?
What version fixes CVE-2026-98265?
What CWE is associated with CVE-2026-98265?
How can I check Maven dependencies for CVE-2026-98265?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qghg-5w48-4c7c",
"modified" : "2026-10-06T09:31:32Z",
"published" : "2026-10-06T09:31:32Z",
"aliases" : [ "CVE-2026-98265" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Clamp implicit feedback packet count to URB capacity\n\ndata_ep_set_params() allocates each data URB for exactly u->packets\nisochronous frames, so urb->iso_frame_desc[] has u->packets slots and\nctx->packets is the driver's only record of that limit. For an implicit\nfeedback sink, snd_usb_queue_pending_output_urbs() overwrites it with the\nsync source's packet count, which is calculated independently from the\ncapture endpoint's parameters. When that count is larger,\nprepare_playback_urb() and prepare_silent_urb() can write\niso_frame_desc[] past the allocation; their existing bounds limit payload\nbytes, not the descriptor index.\n\nThe reproducer uses a high-speed UAC2 device declaring bInterval 1 for\nimplicit feedback capture (8 packets) and bInterval 4 for playback\n(1 packet). On the first capture completion after the stream starts, it\naccesses seven descriptors spanning 112 bytes beyond the one-packet URB:\n\n BUG: KASAN: slab-out-of-bounds in prepare_playback_urb (sound/usb/pcm.c:1560)\n Write of size 4 at addr ffff88801e696ad0 by task vhci_rx/178\n prepare_playback_urb (sound/usb/pcm.c:1560)\n prepare_outbound_urb (sound/usb/endpoint.c:340)\n snd_usb_queue_pending_output_urbs (sound/usb/endpoint.c:501)\n snd_complete_urb (sound/usb/endpoint.c:1834)\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)\n kthread (kernel/kthread.c:436)\n The buggy address belongs to the object at ffff88801e696a00\n which belongs to the cache kmalloc-256 of size 256\n The buggy address is located 0 bytes to the right of\n allocated 208-byte region [ffff88801e696a00, ffff88801e696ad0)\n\nRecord the allocated packet count per endpoint and clamp both the adopted\ncount and the packet-size copy to it. Fold the Format Type II delimiter\ninto urb_packs before the allocation loop so the recorded limit matches\nevery URB.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98265"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/76a986c980bb502c7688d605ac7a67fd257a9a1b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/79c55a7b5d71cf2a6bbd4bd7698e1b10b70f813a"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ab77e3f453c5f2499c08d6e8e218501d25bab39e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/ad279ba0dc1781229f5b52f58d38d56960400e06"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-06T09:18:15Z"
}
}