CVE-2026-80939: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-q754-7p54-36jv
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80939
GHSA Identifier GHSA-q754-7p54-36jv
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-80939

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-80939, 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: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot Since the hardware rfkill polling was introduced, arm64 platforms can panic with an asynchronous SError during warm reboot: SError Interrupt on CPU8, code 0x00000000be000011 -- SError Workqueue: events_power_efficient rfkill_poll [rfkill] rtw89_pci_ops_read8+0x94/0x160 [rtw89_pci] rtw89_core_rfkill_poll+0x50/0x1e0 [rtw89_core] rtw89_ops_rfkill_poll+0x40/0x68 [rtw89_core] ieee80211_rfkill_poll+0x3c/0x70 [mac80211] cfg80211_rfkill_poll+0x40/0x2a0 [cfg80211] rfkill_poll+0x30/0x88 [rfkill] Kernel panic - not syncing: Asynchronous SError Interrupt On the reboot path the kernel only runs device_shutdown(), which calls each driver's .shutdown callback; .remove is not invoked. The rtw89 PCI driver had no .shutdown callback, so nothing stopped the rfkill polling work while the platform was tearing the PCIe link down. Once the link is gone, the next MMIO read from the poll handler targets a non-responding device and is reported as a fatal asynchronous SError on arm64. Add rtw89_pci_shutdown(), wired to all rtw89 PCI device drivers, which sets a new RTW89_FLAG_SHUTDOWN flag (mirroring the USB RTW89_FLAG_UNPLUGGED pattern). When the flag is set, rtw89_ops_rfkill_poll() returns early, so no MMIO read is issued to the chip after shutdown begins and the SError no longer occurs. This does not call the full .remove path from .shutdown, to keep the shutdown handler minimal and avoid running the non-idempotent teardown twice.

References

NVD — CVE-2026-80939 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80939
git.kernel.org/stable/c/667c12782a... WEB
https://git.kernel.org/stable/c/667c12782aaf8dd3cb2213e528fe63a73cb63345
git.kernel.org/stable/c/9693980cd7... WEB
https://git.kernel.org/stable/c/9693980cd7d2f5b17e5ef5922b922f2e1a770fca
git.kernel.org/stable/c/c1f214dd13... WEB
https://git.kernel.org/stable/c/c1f214dd1351244156deb57761b14190a233aef6
git.kernel.org/stable/c/dfe2b5b205... WEB
https://git.kernel.org/stable/c/dfe2b5b2056918d186ad890079a9e7ec1898429a

Frequently Asked Questions

What is CVE-2026-80939?
CVE-2026-80939 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-80939?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80939?
CVE-2026-80939 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80939?
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-q754-7p54-36jv",
  "modified" : "2026-10-03T12:31:05Z",
  "published" : "2026-09-11T21:31:20Z",
  "aliases" : [ "CVE-2026-80939" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot\n\nSince the hardware rfkill polling was introduced, arm64 platforms can\npanic with an asynchronous SError during warm reboot:\n\n  SError Interrupt on CPU8, code 0x00000000be000011 -- SError\n  Workqueue: events_power_efficient rfkill_poll [rfkill]\n    rtw89_pci_ops_read8+0x94/0x160 [rtw89_pci]\n    rtw89_core_rfkill_poll+0x50/0x1e0 [rtw89_core]\n    rtw89_ops_rfkill_poll+0x40/0x68 [rtw89_core]\n    ieee80211_rfkill_poll+0x3c/0x70 [mac80211]\n    cfg80211_rfkill_poll+0x40/0x2a0 [cfg80211]\n    rfkill_poll+0x30/0x88 [rfkill]\n  Kernel panic - not syncing: Asynchronous SError Interrupt\n\nOn the reboot path the kernel only runs device_shutdown(), which calls\neach driver's .shutdown callback; .remove is not invoked.  The rtw89 PCI\ndriver had no .shutdown callback, so nothing stopped the rfkill polling\nwork while the platform was tearing the PCIe link down.  Once the link\nis gone, the next MMIO read from the poll handler targets a\nnon-responding device and is reported as a fatal asynchronous SError on\narm64.\n\nAdd rtw89_pci_shutdown(), wired to all rtw89 PCI device drivers, which\nsets a new RTW89_FLAG_SHUTDOWN flag (mirroring the USB\nRTW89_FLAG_UNPLUGGED pattern).  When the flag is set,\nrtw89_ops_rfkill_poll() returns early, so no MMIO read is issued to the\nchip after shutdown begins and the SError no longer occurs.\n\nThis does not call the full .remove path from .shutdown, to keep the\nshutdown handler minimal and avoid running the non-idempotent teardown\ntwice.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80939"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/667c12782aaf8dd3cb2213e528fe63a73cb63345"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9693980cd7d2f5b17e5ef5922b922f2e1a770fca"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c1f214dd1351244156deb57761b14190a233aef6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dfe2b5b2056918d186ad890079a9e7ec1898429a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:18:58Z"
  }
}