<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T07:55:55.043011+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-68179</id>
    <title>CVE-2026-68179 — misc: nsm: only unlock nsm_dev on post-lock error paths</title>
    <updated>2026-09-30T07:55:55.060133+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>misc: nsm: only unlock nsm_dev on post-lock error paths</p>
<p>nsm_dev_ioctl() jumps to the common out label even when the initial
copy_from_user() fails before nsm-&gt;lock has been taken.  The error path
then blindly unlocks a mutex that was never acquired.</p>
<p>This issue was found by our static analysis tool and then manually
reviewed against the current tree.</p>
<p>The grounded PoC kept the miscdevice ioctl entry and the pre-lock
copy_from_user(&amp;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(&amp;nsm-&gt;lock).  Lockdep reported:</p>
<p>WARNING: bad unlock balance detected!
  exploit/193 is trying to release lock (&amp;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.</p>
<p>Return immediately on the pre-lock copy_from_user() failure and keep the
common unlock label for the post-lock paths only.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68179"/>
  </entry>
</feed>
