CVE-2026-80999: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-5x4g-x6mc-9fxq
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80999
GHSA Identifier GHSA-5x4g-x6mc-9fxq
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-80999

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-80999, 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: net: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO rtl83xx_reset_assert() and rtl83xx_reset_deassert() are only called from the probe path, which may sleep and is not timing-critical. When the reset GPIO is provided by a sleeping controller such as an I2C I/O expander, gpiod_set_value() warns: WARNING: drivers/gpio/gpiolib.c:4030 at gpiod_set_value+0x44/0x80, CPU#1: kworker/u16:4/61 Hardware name: B&O MAP CA33 Rev f (UNKNOWN) (DT) Workqueue: events_unbound deferred_probe_work_func pc : gpiod_set_value+0x44/0x80 lr : rtl83xx_probe+0x1d8/0x3a0 Call trace: gpiod_set_value+0x44/0x80 (P) rtl83xx_probe+0x1d8/0x3a0 realtek_mdio_probe+0x24/0xa0 mdio_probe+0x38/0x78 really_probe+0xc4/0x3e0 __driver_probe_device+0x15c/0x1b8 driver_probe_device+0xb4/0x120 __device_attach_driver+0xb8/0x1a0 bus_for_each_drv+0x88/0xf0 __device_attach+0xa0/0x1d8 device_initial_probe+0x54/0x68 bus_probe_device+0x38/0xa0 deferred_probe_work_func+0xb8/0x120 process_one_work+0x184/0x4e8 worker_thread+0x188/0x308 kthread+0x130/0x150 ret_from_fork+0x10/0x20 Switch both helpers to gpiod_set_value_cansleep() so such a reset GPIO can be used without triggering the warning. The reset GPIO has been driven with the non-sleeping gpiod_set_value() since the driver was added in v4.19. The call has since been refactored across several files - from realtek-smi.c / realtek-mdio.c into the common rtl83xx.c module and then into the rtl83xx_reset_assert() and rtl83xx_reset_deassert() helpers (both in v6.9). This patch therefore applies as-is only to kernels that carry those helpers (v6.9+); older stable kernels need the same gpiod_set_value_cansleep() conversion at the corresponding open-coded call sites.

References

NVD — CVE-2026-80999 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80999
git.kernel.org/stable/c/1610a8c2b9... WEB
https://git.kernel.org/stable/c/1610a8c2b93e815e3dc8643a2a69ab1c37975a6a
git.kernel.org/stable/c/c32cf5292a... WEB
https://git.kernel.org/stable/c/c32cf5292a0dd70c4afc138b4dc45743a190cd5a
git.kernel.org/stable/c/f71087e7c6... WEB
https://git.kernel.org/stable/c/f71087e7c63aa3e99bf65d7ddf91eb4fd3545778
git.kernel.org/stable/c/fb58b6a696... WEB
https://git.kernel.org/stable/c/fb58b6a696b30bcbfbe0cfc0a91b19c816a955fc

Frequently Asked Questions

What is CVE-2026-80999?
CVE-2026-80999 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-80999?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80999?
CVE-2026-80999 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80999?
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-5x4g-x6mc-9fxq",
  "modified" : "2026-09-11T21:31:23Z",
  "published" : "2026-09-11T21:31:23Z",
  "aliases" : [ "CVE-2026-80999" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO\n\nrtl83xx_reset_assert() and rtl83xx_reset_deassert() are only called from\nthe probe path, which may sleep and is not timing-critical.  When the\nreset GPIO is provided by a sleeping controller such as an I2C I/O\nexpander, gpiod_set_value() warns:\n\n  WARNING: drivers/gpio/gpiolib.c:4030 at gpiod_set_value+0x44/0x80, CPU#1: kworker/u16:4/61\n  Hardware name: B&O MAP CA33 Rev f (UNKNOWN) (DT)\n  Workqueue: events_unbound deferred_probe_work_func\n  pc : gpiod_set_value+0x44/0x80\n  lr : rtl83xx_probe+0x1d8/0x3a0\n  Call trace:\n   gpiod_set_value+0x44/0x80 (P)\n   rtl83xx_probe+0x1d8/0x3a0\n   realtek_mdio_probe+0x24/0xa0\n   mdio_probe+0x38/0x78\n   really_probe+0xc4/0x3e0\n   __driver_probe_device+0x15c/0x1b8\n   driver_probe_device+0xb4/0x120\n   __device_attach_driver+0xb8/0x1a0\n   bus_for_each_drv+0x88/0xf0\n   __device_attach+0xa0/0x1d8\n   device_initial_probe+0x54/0x68\n   bus_probe_device+0x38/0xa0\n   deferred_probe_work_func+0xb8/0x120\n   process_one_work+0x184/0x4e8\n   worker_thread+0x188/0x308\n   kthread+0x130/0x150\n   ret_from_fork+0x10/0x20\n\nSwitch both helpers to gpiod_set_value_cansleep() so such a reset GPIO can\nbe used without triggering the warning.\n\nThe reset GPIO has been driven with the non-sleeping gpiod_set_value()\nsince the driver was added in v4.19.  The call has since been refactored\nacross several files - from realtek-smi.c / realtek-mdio.c into the common\nrtl83xx.c module and then into the rtl83xx_reset_assert() and\nrtl83xx_reset_deassert() helpers (both in v6.9).  This patch therefore\napplies as-is only to kernels that carry those helpers (v6.9+); older\nstable kernels need the same gpiod_set_value_cansleep() conversion at the\ncorresponding open-coded call sites.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80999"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1610a8c2b93e815e3dc8643a2a69ab1c37975a6a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c32cf5292a0dd70c4afc138b4dc45743a190cd5a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f71087e7c63aa3e99bf65d7ddf91eb4fd3545778"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fb58b6a696b30bcbfbe0cfc0a91b19c816a955fc"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:07Z"
  }
}