CVE-2026-98741: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-3vm7-3m85-mm4q
Share
Published
Advisory Summary

CVE-2026-98741 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-98741 at a Glance

CVE Identifier CVE-2026-98741
GHSA Identifier GHSA-3vm7-3m85-mm4q
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-98741

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-98741, 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: ua101: reject mismatched capture/playback packet sizes detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels. Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes. A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write. Reject such descriptors at probe time. Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected. BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586) Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021 Call Trace: __asan_memset (mm/kasan/shadow.c:84) start_usb_playback (sound/usb/misc/ua101.c:586) playback_pcm_open (sound/usb/misc/ua101.c:679) snd_pcm_open_substream (sound/core/pcm_native.c:2829) snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932) snd_pcm_playback_open (sound/core/pcm_native.c:2891) snd_open (sound/core/sound.c:166) chrdev_open (fs/char_dev.c:411) do_dentry_open (fs/open.c:996) vfs_open (fs/open.c:1101) path_openat (fs/namei.c:4837 fs/namei.c:5000) do_file_open (fs/namei.c:5029) do_sys_openat2 (fs/open.c:1417) __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434) do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The buggy address belongs to the object at ffff8881098f3c00 which belongs to the cache kmalloc-192 of size 192 The buggy address is located 0 bytes inside of allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)

References

NVD — CVE-2026-98741 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98741
git.kernel.org/stable/c/4294fe5704... WEB
https://git.kernel.org/stable/c/4294fe57048594a9e158b61c967bb7f943cda477
git.kernel.org/stable/c/86f86e6fde... WEB
https://git.kernel.org/stable/c/86f86e6fdedc33c5b8d38b9208b350f8accf57ee
git.kernel.org/stable/c/eb0c7fda59... WEB
https://git.kernel.org/stable/c/eb0c7fda59cf650076f8ed5b949a6c8441aa3606
git.kernel.org/stable/c/fd3a7bf0d9... WEB
https://git.kernel.org/stable/c/fd3a7bf0d988b0878a1957df150edb35f81db87e

Frequently Asked Questions

What is CVE-2026-98741?
CVE-2026-98741 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-98741?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98741?
CVE-2026-98741 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98741?
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-3vm7-3m85-mm4q",
  "modified" : "2026-10-18T18:32:02Z",
  "published" : "2026-10-18T18:32:02Z",
  "aliases" : [ "CVE-2026-98741" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: ua101: reject mismatched capture/playback packet sizes\n\ndetect_usb_format() cross-checks bSubframeSize, bBitResolution and\ntSamFreq between the capture and playback interfaces, but never relates\nthe two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB\ngets a buffer of ua->playback.max_packet_bytes, while the number of\nbytes written into it is derived from the capture stream:\ncapture_urb_complete() computes frames from the received capture packet\nand capture.frame_bytes, and start_usb_playback() and playback_work()\nmultiply that by playback.frame_bytes.\n\nA device declaring a large capture wMaxPacketSize with few capture\nchannels and a small playback wMaxPacketSize with many playback channels\ntherefore memset()s and memcpy()s past the end of the playback buffer,\nin open() of the PCM node the driver registers during probe.\nusb_submit_urb() rejects the over-long iso_frame_desc[0].length with\n-EMSGSIZE, but only after the write.\n\nReject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware\ndeclares proportional packet sizes and is unaffected.\n\n  BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)\n  Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021\n  Call Trace:\n   __asan_memset (mm/kasan/shadow.c:84)\n   start_usb_playback (sound/usb/misc/ua101.c:586)\n   playback_pcm_open (sound/usb/misc/ua101.c:679)\n   snd_pcm_open_substream (sound/core/pcm_native.c:2829)\n   snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)\n   snd_pcm_playback_open (sound/core/pcm_native.c:2891)\n   snd_open (sound/core/sound.c:166)\n   chrdev_open (fs/char_dev.c:411)\n   do_dentry_open (fs/open.c:996)\n   vfs_open (fs/open.c:1101)\n   path_openat (fs/namei.c:4837 fs/namei.c:5000)\n   do_file_open (fs/namei.c:5029)\n   do_sys_openat2 (fs/open.c:1417)\n   __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)\n   do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)\n\n  The buggy address belongs to the object at ffff8881098f3c00\n   which belongs to the cache kmalloc-192 of size 192\n  The buggy address is located 0 bytes inside of\n   allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98741"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4294fe57048594a9e158b61c967bb7f943cda477"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/86f86e6fdedc33c5b8d38b9208b350f8accf57ee"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/eb0c7fda59cf650076f8ed5b949a6c8441aa3606"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fd3a7bf0d988b0878a1957df150edb35f81db87e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:27Z"
  }
}