CVE-2026-89881: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-64c5-3gxh-7523
Published
Advisory Summary

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

CVE Identifier CVE-2026-89881
GHSA Identifier GHSA-64c5-3gxh-7523
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-89881

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-89881, 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: media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak rtl2832_sdr_remove() runs on USB disconnect and clears dev->udev to NULL before any pending streaming teardown has run. When user space later closes its file descriptor, vb2 calls rtl2832_sdr_stop_streaming() which in turn calls rtl2832_sdr_free_stream_bufs(). That helper releases each coherent buffer with: usb_free_coherent(dev->udev, dev->buf_size, dev->buf_list[dev->buf_num], dev->dma_addr[dev->buf_num]); usb_free_coherent() returns immediately when its dev argument is NULL, so every DMA stream buffer that was live at disconnect is silently leaked. The URBs allocated in rtl2832_sdr_alloc_urbs() outlive the device for the same reason. The rtl2832_sdr driver uses vb2_fop_release() in its file_operations, so replace video_unregister_device(&dev->vdev) with vb2_video_unregister_device(&dev->vdev) and move it before clearing dev->udev. vb2_video_unregister_device() releases the vb2 queue, which synchronously runs rtl2832_sdr_stop_streaming() if streaming is active, so URBs and coherent DMA stream buffers are freed while dev->udev is still valid. vb2_video_unregister_device() locks vdev->queue->lock (vb_queue_lock) internally, and stop_streaming() locks v4l2_lock, so the previous outer mutex_lock(&dev->vb_queue_lock) / mutex_lock(&dev->v4l2_lock) pair around the unregister sequence would self-deadlock and has been removed. A short v4l2_lock critical section around dev->udev = NULL remains so any ioctl path that still holds the file descriptor sees coherent state. Issue identified by automated review of the INV-003 series at https://sashiko.dev/

References

Frequently Asked Questions

What is CVE-2026-89881?
CVE-2026-89881 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-89881?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89881?
CVE-2026-89881 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89881?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-64c5-3gxh-7523",
  "modified" : "2026-09-16T12:30:40Z",
  "published" : "2026-09-16T12:30:40Z",
  "aliases" : [ "CVE-2026-89881" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak\n\nrtl2832_sdr_remove() runs on USB disconnect and clears dev->udev to\nNULL before any pending streaming teardown has run. When user space\nlater closes its file descriptor, vb2 calls rtl2832_sdr_stop_streaming()\nwhich in turn calls rtl2832_sdr_free_stream_bufs(). That helper releases\neach coherent buffer with:\n\n    usb_free_coherent(dev->udev, dev->buf_size,\n                      dev->buf_list[dev->buf_num],\n                      dev->dma_addr[dev->buf_num]);\n\nusb_free_coherent() returns immediately when its dev argument is NULL,\nso every DMA stream buffer that was live at disconnect is silently\nleaked. The URBs allocated in rtl2832_sdr_alloc_urbs() outlive the\ndevice for the same reason.\n\nThe rtl2832_sdr driver uses vb2_fop_release() in its file_operations,\nso replace video_unregister_device(&dev->vdev) with\nvb2_video_unregister_device(&dev->vdev) and move it before clearing\ndev->udev. vb2_video_unregister_device() releases the vb2 queue, which\nsynchronously runs rtl2832_sdr_stop_streaming() if streaming is active,\nso URBs and coherent DMA stream buffers are freed while dev->udev is\nstill valid.\n\nvb2_video_unregister_device() locks vdev->queue->lock (vb_queue_lock)\ninternally, and stop_streaming() locks v4l2_lock, so the previous outer\nmutex_lock(&dev->vb_queue_lock) / mutex_lock(&dev->v4l2_lock) pair\naround the unregister sequence would self-deadlock and has been removed.\nA short v4l2_lock critical section around dev->udev = NULL remains so\nany ioctl path that still holds the file descriptor sees coherent state.\n\nIssue identified by automated review of the INV-003 series at\nhttps://sashiko.dev/",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89881"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/034b6a4f9589c04bc3f2bd5125658cd72d3e17c8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/053581d4657c6b5289c5de71a4828d313c005189"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0ef9f19010ae4ba93aca211ea8f0081b9bf7aab2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/234c46b95a032232e31fa5987b84fb8f87a9693b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7443b16b6dd8889a3b9c5236a09e7c58f0d11dae"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a0d9d9a3b41a1346c26af57aade6ba3f552fa171"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bbf15e83c37d9ac938b7c35c02b748fe54230010"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dabb047c62668f280998e29117c55e41aabac336"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:16:56Z"
  }
}