CVE-2026-68179 Affecting linux-6.12 package, versions <6.12.101-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LINUX612-18912492
- published18 Aug 2026
- disclosed10 Aug 2026
Introduced: 10 Aug 2026
CVE-2026-68179 (opens in a new tab)How to fix?
Upgrade Echo:latest linux-6.12 to version 6.12.101-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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
- https://advisory.echohq.com/cve/CVE-2026-68179
- https://git.kernel.org/stable/c/4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb
- https://git.kernel.org/stable/c/8f068342096b027181b168d91fef7ac7a2c64b25
- https://git.kernel.org/stable/c/ce1fed11d18e163baf7f875152a33bf80f625c1a
- https://git.kernel.org/stable/c/f318f5a872cb9096536e759b23ae5c9873bb80ed