CVE-2026-80660: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4rpr-p877-fc2p
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-80660
GHSA Identifier GHSA-4rpr-p877-fc2p
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-80660

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-80660, 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: hwmon: (occ) unregister sysfs devices outside occ lock occ_active(false) and occ_shutdown() unregister sysfs-backed devices while occ->lock is held. hwmon_device_unregister() and sysfs_remove_group() can wait for active sysfs callbacks to drain, and those callbacks can enter the OCC update path and try to take occ->lock again. That gives the unregister paths the lock ordering occ->lock -> sysfs callback drain, while a callback has the opposite edge sysfs callback -> occ->lock. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the real unregister and callback carrier: occ_shutdown() hwmon_device_unregister() occ_show_temp_1() occ_update_response() Lockdep reported the circular dependency with occ_shutdown() already holding the OCC mutex and hwmon_device_unregister() waiting on the sysfs side: WARNING: possible circular locking dependency detected ... (sysfs_lock) ... at: hwmon_device_unregister+0x12/0x30 [vuln_msv] ... (&test_occ.lock) ... at: occ_shutdown.constprop.0+0xe/0x40 [vuln_msv] occ_update_response.isra.0+0xb/0x20 [vuln_msv] occ_show_temp_1.constprop.0.isra.0+0x23/0x40 [vuln_msv] *** DEADLOCK *** Serialize hwmon registration and removal with a separate hwmon_lock. Under that lock, detach occ->hwmon and update occ->active while occ->lock is held so concurrent OCC state changes still see a stable state, then drop occ->lock before calling hwmon_device_unregister(). Remove the driver sysfs group before taking occ->lock in occ_shutdown(), so draining the driver attributes cannot wait while the OCC mutex is held. Also make OCC update callbacks return -ENODEV after deactivation, so callbacks that already passed sysfs active protection do not poll the hardware after teardown has detached the hwmon device.

References

NVD — CVE-2026-80660 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-80660
git.kernel.org/stable/c/2092952f22... WEB
https://git.kernel.org/stable/c/2092952f22a7da98e76e84139ae202b1fc7ba899
git.kernel.org/stable/c/2a4c80ff35... WEB
https://git.kernel.org/stable/c/2a4c80ff3571498ec6a916273304b6650026b1b0
git.kernel.org/stable/c/7ee43ec8e6... WEB
https://git.kernel.org/stable/c/7ee43ec8e6774774abbe9dc3027225e01bc964a5
git.kernel.org/stable/c/e314087343... WEB
https://git.kernel.org/stable/c/e31408734332b8cc611342cdaaab6ba492180156
git.kernel.org/stable/c/e7fd81e9fb... WEB
https://git.kernel.org/stable/c/e7fd81e9fb1fe476d2131fec66c1138457810ed4
git.kernel.org/stable/c/f0aad15757... WEB
https://git.kernel.org/stable/c/f0aad157576da199c146c1bb266442befa7912ca

Frequently Asked Questions

What is CVE-2026-80660?
CVE-2026-80660 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-80660?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-80660?
CVE-2026-80660 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-80660?
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-4rpr-p877-fc2p",
  "modified" : "2026-08-28T09:31:48Z",
  "published" : "2026-08-28T09:31:48Z",
  "aliases" : [ "CVE-2026-80660" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (occ) unregister sysfs devices outside occ lock\n\nocc_active(false) and occ_shutdown() unregister sysfs-backed devices while\nocc->lock is held.  hwmon_device_unregister() and sysfs_remove_group() can\nwait for active sysfs callbacks to drain, and those callbacks can enter the\nOCC update path and try to take occ->lock again.  That gives the unregister\npaths the lock ordering occ->lock -> sysfs callback drain, while a callback\nhas the opposite edge sysfs callback -> occ->lock.\n\nThis issue was found by our static analysis tool and then manually\nreviewed against the current tree.\n\nThe grounded PoC kept the real unregister and callback carrier:\n\n  occ_shutdown()\n  hwmon_device_unregister()\n  occ_show_temp_1()\n  occ_update_response()\n\nLockdep reported the circular dependency with occ_shutdown() already\nholding the OCC mutex and hwmon_device_unregister() waiting on the sysfs\nside:\n\n  WARNING: possible circular locking dependency detected\n  ... (sysfs_lock) ... at: hwmon_device_unregister+0x12/0x30 [vuln_msv]\n  ... (&test_occ.lock) ... at: occ_shutdown.constprop.0+0xe/0x40 [vuln_msv]\n  occ_update_response.isra.0+0xb/0x20 [vuln_msv]\n  occ_show_temp_1.constprop.0.isra.0+0x23/0x40 [vuln_msv]\n  *** DEADLOCK ***\n\nSerialize hwmon registration and removal with a separate hwmon_lock.\nUnder that lock, detach occ->hwmon and update occ->active while occ->lock\nis held so concurrent OCC state changes still see a stable state, then\ndrop occ->lock before calling hwmon_device_unregister().  Remove the\ndriver sysfs group before taking occ->lock in occ_shutdown(), so draining\nthe driver attributes cannot wait while the OCC mutex is held.  Also make\nOCC update callbacks return -ENODEV after deactivation, so callbacks that\nalready passed sysfs active protection do not poll the hardware after\nteardown has detached the hwmon device.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-80660"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2092952f22a7da98e76e84139ae202b1fc7ba899"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2a4c80ff3571498ec6a916273304b6650026b1b0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7ee43ec8e6774774abbe9dc3027225e01bc964a5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e31408734332b8cc611342cdaaab6ba492180156"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e7fd81e9fb1fe476d2131fec66c1138457810ed4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f0aad157576da199c146c1bb266442befa7912ca"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-28T08:16:51Z"
  }
}