CVE-2026-68179
HIGHDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-675 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-17638 | Critical | 9.4 | 11% | - | Fix |
| CVE-2026-78663 | High | 7.5 | 0.6% | - | Fix |
| CVE-2026-77860 | Low | 3.7 | 0.3% | - | Fix |
| CVE-2025-68973 | High | 7.8 | 0.2% | - | Fix |
Common questions
How do I fix CVE-2026-68179?
Published advisories record a fix for 134 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-68179 being actively exploited?
Not that we know of. CVE-2026-68179 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.18% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
How severe is CVE-2026-68179?
CVE-2026-68179 has a CVSS v3 base score of 8.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-68179 affect?
Published advisories record a fix for linux (Debian), linux-6.12 (Debian), linux (Ubuntu), linux-aws (Ubuntu), and 130 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-68179
Markdown
[](https://tridentstack.com/cve/CVE-2026-68179)HTML
<a href="https://tridentstack.com/cve/CVE-2026-68179"><img src="https://tridentstack.com/cve/badge/CVE-2026-68179.svg" alt="CVE-2026-68179"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-19.