<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 15:16:06 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-68179</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-68179</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-68179</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>EUVD-2026-353496</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353496</link>
      <description>EUVD-2026-353496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353496</guid>
    </item>
    <item>
      <title>fkie_cve-2026-68179</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-68179</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc: nsm: only unlock nsm_dev on post-lock error paths&lt;/p&gt;
&lt;p&gt;nsm_dev_ioctl() jumps to the common out label even when the initial
copy_from_user() fails before nsm-&amp;gt;lock has been taken.  The error path
then blindly unlocks a mutex that was never acquired.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the miscdevice ioctl entry and the pre-lock
copy_from_user(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:&lt;/p&gt;
&lt;p&gt;WARNING: bad unlock balance detected!
  exploit/193 is trying to release lock (&amp;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.&lt;/p&gt;
&lt;p&gt;Return immediately on the pre-lock copy_from_user() failure and keep the
common unlock label for the post-lock paths only.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc: nsm: only unlock nsm_dev on post-lock error paths&lt;/p&gt;
&lt;p&gt;nsm_dev_ioctl() jumps to the common out label even when the initial
copy_from_user() fails before nsm-&amp;gt;lock has been taken.  The error path
then blindly unlocks a mutex that was never acquired.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the miscdevice ioctl entry and the pre-lock
copy_from_user(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:&lt;/p&gt;
&lt;p&gt;WARNING: bad unlock balance detected!
  exploit/193 is trying to release lock (&amp;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.&lt;/p&gt;
&lt;p&gt;Return immediately on the pre-lock copy_from_user() failure and keep the
common unlock label for the post-lock paths only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-68179</guid>
    </item>
    <item>
      <title>GHSA-3jf9-7qhv-4pm6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3jf9-7qhv-4pm6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc: nsm: only unlock nsm_dev on post-lock error paths&lt;/p&gt;
&lt;p&gt;nsm_dev_ioctl() jumps to the common out label even when the initial
copy_from_user() fails before nsm-&amp;gt;lock has been taken.  The error path
then blindly unlocks a mutex that was never acquired.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the miscdevice ioctl entry and the pre-lock
copy_from_user(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:&lt;/p&gt;
&lt;p&gt;WARNING: bad unlock balance detected!
  exploit/193 is trying to release lock (&amp;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.&lt;/p&gt;
&lt;p&gt;Return immediately on the pre-lock copy_from_user() failure and keep the
common unlock label for the post-lock paths only.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;misc: nsm: only unlock nsm_dev on post-lock error paths&lt;/p&gt;
&lt;p&gt;nsm_dev_ioctl() jumps to the common out label even when the initial
copy_from_user() fails before nsm-&amp;gt;lock has been taken.  The error path
then blindly unlocks a mutex that was never acquired.&lt;/p&gt;
&lt;p&gt;This issue was found by our static analysis tool and then manually
reviewed against the current tree.&lt;/p&gt;
&lt;p&gt;The grounded PoC kept the miscdevice ioctl entry and the pre-lock
copy_from_user(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:&lt;/p&gt;
&lt;p&gt;WARNING: bad unlock balance detected!
  exploit/193 is trying to release lock (&amp;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.&lt;/p&gt;
&lt;p&gt;Return immediately on the pre-lock copy_from_user() failure and keep the
common unlock label for the post-lock paths only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3jf9-7qhv-4pm6</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68179</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68179</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;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-&amp;gt;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(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:   WARNING: bad unlock balance detected!   exploit/193 is trying to release lock (&amp;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. Return immediately on the pre-lock copy_from_user() failure and keep the common unlock label for the post-lock paths only.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 154 more&lt;/p&gt;
&lt;p&gt;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-&amp;gt;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(&amp;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;amp;nsm-&amp;gt;lock).  Lockdep reported:   WARNING: bad unlock balance detected!   exploit/193 is trying to release lock (&amp;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. Return immediately on the pre-lock copy_from_user() failure and keep the common unlock label for the post-lock paths only.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68179</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2730 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</guid>
    </item>
  </channel>
</rss>
