<?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 20:10:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72127</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72127</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-72127</guid>
    </item>
    <item>
      <title>EUVD-2026-353667</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353667</link>
      <description>EUVD-2026-353667</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353667</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72127</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72127</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace&lt;/p&gt;
&lt;p&gt;netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID
using task_pid_nr(), which returns the PID in the initial pid namespace.&lt;/p&gt;
&lt;p&gt;NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family
is netnsok, so a caller in a child pid namespace can issue it. That caller
then sees the kthread&amp;#39;s global PID, even though the kthread is not visible
in its pid namespace, where the value should be 0.&lt;/p&gt;
&lt;p&gt;Translate the PID through the caller&amp;#39;s pid namespace, the same way commit
3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s
pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both
run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is
the caller&amp;#39;s pid namespace.&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;netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace&lt;/p&gt;
&lt;p&gt;netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID
using task_pid_nr(), which returns the PID in the initial pid namespace.&lt;/p&gt;
&lt;p&gt;NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family
is netnsok, so a caller in a child pid namespace can issue it. That caller
then sees the kthread&amp;#39;s global PID, even though the kthread is not visible
in its pid namespace, where the value should be 0.&lt;/p&gt;
&lt;p&gt;Translate the PID through the caller&amp;#39;s pid namespace, the same way commit
3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s
pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both
run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is
the caller&amp;#39;s pid namespace.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72127</guid>
    </item>
    <item>
      <title>GHSA-hx9w-mw8p-76q2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hx9w-mw8p-76q2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace&lt;/p&gt;
&lt;p&gt;netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID
using task_pid_nr(), which returns the PID in the initial pid namespace.&lt;/p&gt;
&lt;p&gt;NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family
is netnsok, so a caller in a child pid namespace can issue it. That caller
then sees the kthread&amp;#39;s global PID, even though the kthread is not visible
in its pid namespace, where the value should be 0.&lt;/p&gt;
&lt;p&gt;Translate the PID through the caller&amp;#39;s pid namespace, the same way commit
3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s
pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both
run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is
the caller&amp;#39;s pid namespace.&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;netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace&lt;/p&gt;
&lt;p&gt;netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID
using task_pid_nr(), which returns the PID in the initial pid namespace.&lt;/p&gt;
&lt;p&gt;NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family
is netnsok, so a caller in a child pid namespace can issue it. That caller
then sees the kthread&amp;#39;s global PID, even though the kthread is not visible
in its pid namespace, where the value should be 0.&lt;/p&gt;
&lt;p&gt;Translate the PID through the caller&amp;#39;s pid namespace, the same way commit
3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s
pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both
run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is
the caller&amp;#39;s pid namespace.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hx9w-mw8p-76q2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72127</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72127</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: netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID using task_pid_nr(), which returns the PID in the initial pid namespace. NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family is netnsok, so a caller in a child pid namespace can issue it. That caller then sees the kthread&amp;#39;s global PID, even though the kthread is not visible in its pid namespace, where the value should be 0. Translate the PID through the caller&amp;#39;s pid namespace, the same way commit 3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is the caller&amp;#39;s pid namespace.&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: netdev-genl: report NAPI thread PID in the caller&amp;#39;s pid namespace netdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID using task_pid_nr(), which returns the PID in the initial pid namespace. NETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family is netnsok, so a caller in a child pid namespace can issue it. That caller then sees the kthread&amp;#39;s global PID, even though the kthread is not visible in its pid namespace, where the value should be 0. Translate the PID through the caller&amp;#39;s pid namespace, the same way commit 3799c2570982 (&amp;#34;io_uring/fdinfo: translate SqThread PID through caller&amp;#39;s pid_ns&amp;#34;) did for the io_uring SQPOLL thread. The doit and dumpit paths both run synchronously in the caller&amp;#39;s context, so task_active_pid_ns(current) is the caller&amp;#39;s pid namespace.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72127</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
