<?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>Tue, 17 Nov 2026 10:09:47 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98983</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98983</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98983</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</link>
      <description>certfr-2026-avi-1537</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</guid>
    </item>
    <item>
      <title>EUVD-2026-391545</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391545</link>
      <description>EUVD-2026-391545</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391545</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98983</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98983</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;unshare: don&amp;#39;t drop active namespace references that were never taken&lt;/p&gt;
&lt;p&gt;Active references on the namespaces of an nsproxy are taken when the
nsproxy is installed into a task in switch_task_namespaces() and
copy_namespaces() and dropped again by put_nsproxy() through
deactivate_nsproxy().&lt;/p&gt;
&lt;p&gt;But ksys_unshare() calls put_nsproxy() on an nsproxy that was never
installed when set_cred_ucounts() fails. The new namespaces of that
nsproxy go from zero to minus one and the namespaces shared with the
caller lose a reference that belongs to the nsproxy the caller keeps
using:&lt;/p&gt;
&lt;p&gt;WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230
   nsproxy_ns_active_put
   deactivate_nsproxy
   ksys_unshare&lt;/p&gt;
&lt;p&gt;Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns()
anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t
allocate and it only allocates when the real uid of the caller differs
from its effective uid.&lt;/p&gt;
&lt;p&gt;Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify
create_new_namespaces()&amp;#34;) separated the two cases on purpose.
nsproxy_free() frees an nsproxy that was prepared but never installed
and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use
it for a failed unshare() as well.&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;unshare: don&amp;#39;t drop active namespace references that were never taken&lt;/p&gt;
&lt;p&gt;Active references on the namespaces of an nsproxy are taken when the
nsproxy is installed into a task in switch_task_namespaces() and
copy_namespaces() and dropped again by put_nsproxy() through
deactivate_nsproxy().&lt;/p&gt;
&lt;p&gt;But ksys_unshare() calls put_nsproxy() on an nsproxy that was never
installed when set_cred_ucounts() fails. The new namespaces of that
nsproxy go from zero to minus one and the namespaces shared with the
caller lose a reference that belongs to the nsproxy the caller keeps
using:&lt;/p&gt;
&lt;p&gt;WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230
   nsproxy_ns_active_put
   deactivate_nsproxy
   ksys_unshare&lt;/p&gt;
&lt;p&gt;Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns()
anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t
allocate and it only allocates when the real uid of the caller differs
from its effective uid.&lt;/p&gt;
&lt;p&gt;Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify
create_new_namespaces()&amp;#34;) separated the two cases on purpose.
nsproxy_free() frees an nsproxy that was prepared but never installed
and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use
it for a failed unshare() as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98983</guid>
    </item>
    <item>
      <title>GHSA-vc4v-q632-x9g5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vc4v-q632-x9g5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;unshare: don&amp;#39;t drop active namespace references that were never taken&lt;/p&gt;
&lt;p&gt;Active references on the namespaces of an nsproxy are taken when the
nsproxy is installed into a task in switch_task_namespaces() and
copy_namespaces() and dropped again by put_nsproxy() through
deactivate_nsproxy().&lt;/p&gt;
&lt;p&gt;But ksys_unshare() calls put_nsproxy() on an nsproxy that was never
installed when set_cred_ucounts() fails. The new namespaces of that
nsproxy go from zero to minus one and the namespaces shared with the
caller lose a reference that belongs to the nsproxy the caller keeps
using:&lt;/p&gt;
&lt;p&gt;WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230
   nsproxy_ns_active_put
   deactivate_nsproxy
   ksys_unshare&lt;/p&gt;
&lt;p&gt;Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns()
anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t
allocate and it only allocates when the real uid of the caller differs
from its effective uid.&lt;/p&gt;
&lt;p&gt;Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify
create_new_namespaces()&amp;#34;) separated the two cases on purpose.
nsproxy_free() frees an nsproxy that was prepared but never installed
and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use
it for a failed unshare() as well.&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;unshare: don&amp;#39;t drop active namespace references that were never taken&lt;/p&gt;
&lt;p&gt;Active references on the namespaces of an nsproxy are taken when the
nsproxy is installed into a task in switch_task_namespaces() and
copy_namespaces() and dropped again by put_nsproxy() through
deactivate_nsproxy().&lt;/p&gt;
&lt;p&gt;But ksys_unshare() calls put_nsproxy() on an nsproxy that was never
installed when set_cred_ucounts() fails. The new namespaces of that
nsproxy go from zero to minus one and the namespaces shared with the
caller lose a reference that belongs to the nsproxy the caller keeps
using:&lt;/p&gt;
&lt;p&gt;WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230
   nsproxy_ns_active_put
   deactivate_nsproxy
   ksys_unshare&lt;/p&gt;
&lt;p&gt;Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns()
anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t
allocate and it only allocates when the real uid of the caller differs
from its effective uid.&lt;/p&gt;
&lt;p&gt;Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify
create_new_namespaces()&amp;#34;) separated the two cases on purpose.
nsproxy_free() frees an nsproxy that was prepared but never installed
and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use
it for a failed unshare() as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vc4v-q632-x9g5</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98983</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98983</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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: unshare: don&amp;#39;t drop active namespace references that were never taken Active references on the namespaces of an nsproxy are taken when the nsproxy is installed into a task in switch_task_namespaces() and copy_namespaces() and dropped again by put_nsproxy() through deactivate_nsproxy(). But ksys_unshare() calls put_nsproxy() on an nsproxy that was never installed when set_cred_ucounts() fails. The new namespaces of that nsproxy go from zero to minus one and the namespaces shared with the caller lose a reference that belongs to the nsproxy the caller keeps using:   WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230    nsproxy_ns_active_put    deactivate_nsproxy    ksys_unshare Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns() anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t allocate and it only allocates when the real uid of the caller differs from its effective uid. Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify create_new_namespaces()&amp;#34;) separated the two cases on purpose. nsproxy_free() frees an nsproxy that was prepared but never installed and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use it for a failed unshare() as well.&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 197 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: unshare: don&amp;#39;t drop active namespace references that were never taken Active references on the namespaces of an nsproxy are taken when the nsproxy is installed into a task in switch_task_namespaces() and copy_namespaces() and dropped again by put_nsproxy() through deactivate_nsproxy(). But ksys_unshare() calls put_nsproxy() on an nsproxy that was never installed when set_cred_ucounts() fails. The new namespaces of that nsproxy go from zero to minus one and the namespaces shared with the caller lose a reference that belongs to the nsproxy the caller keeps using:   WARNING: kernel/nscommon.c:171 at __ns_ref_active_put+0x1cd/0x230    nsproxy_ns_active_put    deactivate_nsproxy    ksys_unshare Afterwards the namespaces the caller lives in aren&amp;#39;t listed by listns() anymore. set_cred_ucounts() only fails when alloc_ucounts() can&amp;#39;t allocate and it only allocates when the real uid of the caller differs from its effective uid. Commit cefd55bd2159 (&amp;#34;nsproxy: fix free_nsproxy() and simplify create_new_namespaces()&amp;#34;) separated the two cases on purpose. nsproxy_free() frees an nsproxy that was prepared but never installed and that&amp;#39;s what a failed setns() uses in put_nsset(). Export it and use it for a failed unshare() as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98983</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&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, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
