CVE-2026-68179: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-3jf9-7qhv-4pm6
Share
CVSS 8.4
CWE-675
Published
Advisory Summary

CVE-2026-68179 is a HIGH (CVSS 8.4) security vulnerability vulnerability (CWE-675: Multiple Operations on Resource in Single-Operation Context) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product performs the same operation on a resource two or more times, when the operation should only be applied once.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68179 at a Glance

CVE Identifier CVE-2026-68179
GHSA Identifier GHSA-3jf9-7qhv-4pm6
Severity HIGH
CVSS v3.1 Base Score 8.4
CWE Classification CWE-675: Multiple Operations on Resource in Single-Operation Context
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.4

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-68179

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-68179, 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 CWE-675: Multiple Operations on Resource in Single-Operation Context, where the product performs the same operation on a resource two or more times, when the operation should only be applied once. 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: misc: nsm: only unlock nsm_dev on post-lock error paths nsm_dev_ioctl() jumps to the common out label even when the initial copy_from_user() fails before nsm->lock has been taken. The error path then blindly unlocks a mutex that was never acquired. This issue was found by our static analysis tool and then manually reviewed against the current tree. The grounded PoC kept the miscdevice ioctl entry and the pre-lock copy_from_user(&raw, argp, _IOC_SIZE(cmd)) failure path by issuing NSM_IOCTL_RAW with an invalid user pointer. That failure reaches the shared out label before mutex_lock(&nsm->lock). Lockdep reported: WARNING: bad unlock balance detected! exploit/193 is trying to release lock (&global_nsm.lock) at: nsm_dev_ioctl+0x5f/0xcf [vuln_msv] but there are no more locks to release! no locks held by exploit/193. Return immediately on the pre-lock copy_from_user() failure and keep the common unlock label for the post-lock paths only.

References

NVD — CVE-2026-68179 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68179
git.kernel.org/stable/c/4aa3f7d48e... WEB
https://git.kernel.org/stable/c/4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb
git.kernel.org/stable/c/8f06834209... WEB
https://git.kernel.org/stable/c/8f068342096b027181b168d91fef7ac7a2c64b25
git.kernel.org/stable/c/ce1fed11d1... WEB
https://git.kernel.org/stable/c/ce1fed11d18e163baf7f875152a33bf80f625c1a
git.kernel.org/stable/c/f318f5a872... WEB
https://git.kernel.org/stable/c/f318f5a872cb9096536e759b23ae5c9873bb80ed

Frequently Asked Questions

What is CVE-2026-68179?
CVE-2026-68179 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-675: Multiple Operations on Resource in Single-Operation Context.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68179?
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-68179?
CVE-2026-68179 has a CVSS v3.1 base score of 8.4 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-68179?
CVE-2026-68179 is classified under CWE-675: Multiple Operations on Resource in Single-Operation Context (The product performs the same operation on a resource two or more times, when the operation should only be applied once.).
How can I check Maven dependencies for CVE-2026-68179?
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-3jf9-7qhv-4pm6",
  "modified" : "2026-08-14T00:31:52Z",
  "published" : "2026-08-10T15:33:40Z",
  "aliases" : [ "CVE-2026-68179" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: nsm: only unlock nsm_dev on post-lock error paths\n\nnsm_dev_ioctl() jumps to the common out label even when the initial\ncopy_from_user() fails before nsm->lock has been taken.  The error path\nthen blindly unlocks a mutex that was never acquired.\n\nThis issue was found by our static analysis tool and then manually\nreviewed against the current tree.\n\nThe grounded PoC kept the miscdevice ioctl entry and the pre-lock\ncopy_from_user(&raw, argp, _IOC_SIZE(cmd)) failure path by issuing\nNSM_IOCTL_RAW with an invalid user pointer.  That failure reaches the\nshared out label before mutex_lock(&nsm->lock).  Lockdep reported:\n\n  WARNING: bad unlock balance detected!\n  exploit/193 is trying to release lock (&global_nsm.lock) at:\n  nsm_dev_ioctl+0x5f/0xcf [vuln_msv]\n  but there are no more locks to release!\n  no locks held by exploit/193.\n\nReturn immediately on the pre-lock copy_from_user() failure and keep the\ncommon unlock label for the post-lock paths only.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68179"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8f068342096b027181b168d91fef7ac7a2c64b25"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ce1fed11d18e163baf7f875152a33bf80f625c1a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f318f5a872cb9096536e759b23ae5c9873bb80ed"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-675" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:04Z"
  }
}