CVE-2026-68179
CVE CVE-2026-68179EUVD EUVD-2026-55280Published 2026-08-10T11:59:50.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux b9873755a6c8ccfce79094c4dce9efa3ecb1a749 <8f068342096b027181b168d91fef7ac7a2c64b25; b9873755a6c8ccfce79094c4dce9efa3ecb1a749 <f318f5a872cb9096536e759b23ae5c9873bb80ed; patch: 7.2-rc5; patch: 6.18.42; patch: 6.12.101; b9873755a6c8ccfce79094c4dce9efa3ecb1a749 <ce1fed11d18e163baf7f875152a33bf80f625c1a; 6.8; patch: 0; b9873755a6c8ccfce79094c4dce9efa3ecb1a749 <4aa3f7d48e91eb74a363c1b4d7dbdd28f5b341fb; patch: 7.1.6
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.