CVE-2026-89880: Software Security Vulnerability Vulnerability

HIGH

Advisory Identifier: GHSA-rq55-pff5-xw57

CVSS 7.8

Published 2026-09-16

Advisory Summary

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

CVE-2026-89880 at a Glance

CVE Identifier CVE-2026-89880

GHSA Identifier GHSA-rq55-pff5-xw57

Severity HIGH

CVSS v3.1 Base Score 7.8

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-16

Last Updated 2026-09-16

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)

Attack Complexity Low (AC:L)

Privileges Required Low (PR:L)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality High (C:H)

Integrity High (I:H)

Availability High (A:H)

How to Fix CVE-2026-89880

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-89880, 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: release URBs and stream buffers on start_streaming() failure rtl2832_sdr_start_streaming() calls rtl2832_sdr_alloc_stream_bufs(), rtl2832_sdr_alloc_urbs() and rtl2832_sdr_submit_urbs() in sequence and shares a single err: label that only unlocks the mutex and returns. When alloc_urbs() succeeds but submit_urbs() fails, or when alloc_urbs() itself returns -ENOMEM after alloc_stream_bufs() has already succeeded, the URBs and/or the coherent DMA stream buffers stay allocated while streaming reports failure to vb2. Two latent defects follow on the next VIDIOC_STREAMON: 1) rtl2832_sdr_alloc_stream_bufs() unconditionally resets dev->buf_num to 0 and overwrites dev->buf_list[]/dev->dma_addr[], permanently leaking the coherent DMA memory allocated by the previous attempt. 2) rtl2832_sdr_alloc_urbs() never resets dev->urbs_initialized and only increments it. After a second successful pass urbs_initialized can exceed MAX_BULK_BUFS, so the subsequent rtl2832_sdr_free_urbs() walks from urbs_initialized - 1 down to 0 and reads past the end of dev->urb_list[], passing garbage pointers to usb_free_urb(). Mirror the teardown that stop_streaming() already performs: on the error path call rtl2832_sdr_free_urbs() and rtl2832_sdr_free_stream_bufs() before unlocking. Both helpers are idempotent (free_urbs kills and zeros urbs_initialized; free_stream_bufs is gated on URB_BUF and clears the buf_num counter), so partial-failure paths and the no-allocation paths remain safe. Issue identified by automated review of the INV-003 series at https://sashiko.dev/

References

NVD — CVE-2026-89880 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-89880

git.kernel.org/stable/c/0337ab0759... WEB

https://git.kernel.org/stable/c/0337ab0759285076a3f9dcfcc40906e69ab519b3

git.kernel.org/stable/c/26a2a985bb... WEB

https://git.kernel.org/stable/c/26a2a985bbeee3eaa6f80ff7de732161a171ec9f

git.kernel.org/stable/c/8bcf11a239... WEB

https://git.kernel.org/stable/c/8bcf11a239eac4e224ad856277de9a36c91b1711

git.kernel.org/stable/c/ac02b2c56c... WEB

https://git.kernel.org/stable/c/ac02b2c56ccef0788cea9b86990a8f349a3fc6d8

git.kernel.org/stable/c/c819dea3a4... WEB

https://git.kernel.org/stable/c/c819dea3a433ae790b829443fdcc1715d1586560

git.kernel.org/stable/c/c91e8ae2b3... WEB

https://git.kernel.org/stable/c/c91e8ae2b39c6da81f26f2c9877d3fd33a4465ce

git.kernel.org/stable/c/f14a713a36... WEB

https://git.kernel.org/stable/c/f14a713a36a5c87568430e9770896f2a8f5bbbb7

git.kernel.org/stable/c/fe50cdaebf... WEB

https://git.kernel.org/stable/c/fe50cdaebf12cd32ff9a44d92bfd6fbc2300dbd4

Frequently Asked Questions

What is CVE-2026-89880?

CVE-2026-89880 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-89880?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What is the CVSS score of CVE-2026-89880?

CVE-2026-89880 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

What CWE is associated with CVE-2026-89880?

CVE-2026-89880 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-89880?

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-rq55-pff5-xw57",
  "modified" : "2026-09-16T15:31:00Z",
  "published" : "2026-09-16T12:30:40Z",
  "aliases" : [ "CVE-2026-89880" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure\n\nrtl2832_sdr_start_streaming() calls rtl2832_sdr_alloc_stream_bufs(),\nrtl2832_sdr_alloc_urbs() and rtl2832_sdr_submit_urbs() in sequence and\nshares a single err: label that only unlocks the mutex and returns.\nWhen alloc_urbs() succeeds but submit_urbs() fails, or when alloc_urbs()\nitself returns -ENOMEM after alloc_stream_bufs() has already succeeded,\nthe URBs and/or the coherent DMA stream buffers stay allocated while\nstreaming reports failure to vb2. Two latent defects follow on the next\nVIDIOC_STREAMON:\n\n1) rtl2832_sdr_alloc_stream_bufs() unconditionally resets dev->buf_num\n   to 0 and overwrites dev->buf_list[]/dev->dma_addr[], permanently\n   leaking the coherent DMA memory allocated by the previous attempt.\n\n2) rtl2832_sdr_alloc_urbs() never resets dev->urbs_initialized and only\n   increments it. After a second successful pass urbs_initialized can\n   exceed MAX_BULK_BUFS, so the subsequent rtl2832_sdr_free_urbs() walks\n   from urbs_initialized - 1 down to 0 and reads past the end of\n   dev->urb_list[], passing garbage pointers to usb_free_urb().\n\nMirror the teardown that stop_streaming() already performs: on the error\npath call rtl2832_sdr_free_urbs() and rtl2832_sdr_free_stream_bufs()\nbefore unlocking. Both helpers are idempotent (free_urbs kills and zeros\nurbs_initialized; free_stream_bufs is gated on URB_BUF and clears the\nbuf_num counter), so partial-failure paths and the no-allocation paths\nremain safe.\n\nIssue identified by automated review of the INV-003 series at\nhttps://sashiko.dev/",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89880"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0337ab0759285076a3f9dcfcc40906e69ab519b3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/26a2a985bbeee3eaa6f80ff7de732161a171ec9f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8bcf11a239eac4e224ad856277de9a36c91b1711"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ac02b2c56ccef0788cea9b86990a8f349a3fc6d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c819dea3a433ae790b829443fdcc1715d1586560"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c91e8ae2b39c6da81f26f2c9877d3fd33a4465ce"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f14a713a36a5c87568430e9770896f2a8f5bbbb7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fe50cdaebf12cd32ff9a44d92bfd6fbc2300dbd4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:16:56Z"
  }
}

CVSS V3

7.8 HIGH