CVE-2026-80825: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-82xc-6pqj-mvc4
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80825
GHSA Identifier GHSA-82xc-6pqj-mvc4
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-80825

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-80825, 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: wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb mt7925_usb_sdio_tx_prepare_skb() pushes a TX descriptor and a USB header onto every skb and assumes the headroom for them is already there. That holds for locally generated traffic, where mac80211 reserves hw->extra_tx_headroom, but forwarded frames are sent through ieee80211_8023_xmit(), which does not reserve it. Bridge a wired interface to an mt7925u AP and the first forwarded frame that arrives short panics the kernel: skbuff: skb_under_panic: len:415 put:4 tail:0x19b end:0x640 dev:wlan1 kernel BUG at net/core/skbuff.c:212! Call trace: skb_panic+0x58/0x60 (P) skb_push+0x58/0x60 mt7925_usb_sdio_tx_prepare_skb+0xf8/0x1b8 [mt7925_common] mt76u_tx_queue_skb+0xa0/0x1f8 [mt76_usb] __mt76_tx_queue_skb+0x54/0xe8 [mt76] mt76_txq_schedule.part.0+0x204/0x478 [mt76] mt76_txq_schedule_all+0x50/0x80 [mt76] mt792x_tx_worker+0x68/0x100 [mt792x_lib] __mt76_worker_fn+0x84/0x150 [mt76] Whether a given setup hits it depends on how much headroom the ingress netdev leaves in its rx skbs. Reproduced on a Raspberry Pi 5 bridging onboard ethernet to a Netgear A9000; originally reported on an MT7986 router running OpenWrt. Nick Morrow's testing on a Pi 4 (bcmgenet), which leaves more headroom, helped narrow the trigger to the ingress path. The same bug was fixed on mt7921 by commit 98c4d0abf5c4 ("mt76: mt7921: don't assume adequate headroom for SDIO headers"), but mt7925 was copied from mt7921 without the fix. Add the same guard here.

References

NVD — CVE-2026-80825 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80825
git.kernel.org/stable/c/22edb67861... WEB
https://git.kernel.org/stable/c/22edb6786127271aeba7abd30f152977c605c6a3
git.kernel.org/stable/c/8d481f9358... WEB
https://git.kernel.org/stable/c/8d481f93588932a95f657671d4e1601b90d130cc
git.kernel.org/stable/c/9a72b180f0... WEB
https://git.kernel.org/stable/c/9a72b180f0575e41471e088e09bddc4b73d6dee2
git.kernel.org/stable/c/e5e8fc11a7... WEB
https://git.kernel.org/stable/c/e5e8fc11a7ac578f16079f855b7fffc1649d053c
git.kernel.org/stable/c/ef3e34874d... WEB
https://git.kernel.org/stable/c/ef3e34874d2332d0f63e72c2c35ce5c93568c125

Frequently Asked Questions

What is CVE-2026-80825?
CVE-2026-80825 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-80825?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80825?
CVE-2026-80825 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80825?
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-82xc-6pqj-mvc4",
  "modified" : "2026-09-04T18:31:27Z",
  "published" : "2026-09-04T18:31:27Z",
  "aliases" : [ "CVE-2026-80825" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb\n\nmt7925_usb_sdio_tx_prepare_skb() pushes a TX descriptor and a USB\nheader onto every skb and assumes the headroom for them is already\nthere. That holds for locally generated traffic, where mac80211\nreserves hw->extra_tx_headroom, but forwarded frames are sent through\nieee80211_8023_xmit(), which does not reserve it. Bridge a wired\ninterface to an mt7925u AP and the first forwarded frame that arrives\nshort panics the kernel:\n\n skbuff: skb_under_panic: len:415 put:4 tail:0x19b end:0x640 dev:wlan1\n kernel BUG at net/core/skbuff.c:212!\n Call trace:\n  skb_panic+0x58/0x60 (P)\n  skb_push+0x58/0x60\n  mt7925_usb_sdio_tx_prepare_skb+0xf8/0x1b8 [mt7925_common]\n  mt76u_tx_queue_skb+0xa0/0x1f8 [mt76_usb]\n  __mt76_tx_queue_skb+0x54/0xe8 [mt76]\n  mt76_txq_schedule.part.0+0x204/0x478 [mt76]\n  mt76_txq_schedule_all+0x50/0x80 [mt76]\n  mt792x_tx_worker+0x68/0x100 [mt792x_lib]\n  __mt76_worker_fn+0x84/0x150 [mt76]\n\nWhether a given setup hits it depends on how much headroom the ingress\nnetdev leaves in its rx skbs. Reproduced on a Raspberry Pi 5 bridging\nonboard ethernet to a Netgear A9000; originally reported on an MT7986\nrouter running OpenWrt. Nick Morrow's testing on a Pi 4 (bcmgenet),\nwhich leaves more headroom, helped narrow the trigger to the ingress\npath.\n\nThe same bug was fixed on mt7921 by commit 98c4d0abf5c4 (\"mt76:\nmt7921: don't assume adequate headroom for SDIO headers\"), but mt7925\nwas copied from mt7921 without the fix. Add the same guard here.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80825"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/22edb6786127271aeba7abd30f152977c605c6a3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8d481f93588932a95f657671d4e1601b90d130cc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a72b180f0575e41471e088e09bddc4b73d6dee2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e5e8fc11a7ac578f16079f855b7fffc1649d053c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ef3e34874d2332d0f63e72c2c35ce5c93568c125"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-04T16:18:10Z"
  }
}