<?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>Sun, 04 Oct 2026 05:38:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74383</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74383</guid>
    </item>
    <item>
      <title>EUVD-2026-354200</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354200</link>
      <description>EUVD-2026-354200</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354200</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74383</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74383</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools&lt;/p&gt;
&lt;p&gt;nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the
numa_node forwarded from hctx-&amp;gt;numa_node by its single caller,
nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is
NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the
value becomes UINT_MAX and the index walks off the array (sized to
nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace
without a /dev node.&lt;/p&gt;
&lt;p&gt;Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffff889101603d38
  RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]
  Call Trace:
   nvme_init_hctx+0x10/0x20 [nvme]
   nvme_alloc_ns+0x9e/0xa10 [nvme_core]
   nvme_scan_ns+0x301/0x3b0 [nvme_core]
   nvme_scan_ns_async+0x23/0x30 [nvme_core]&lt;/p&gt;
&lt;p&gt;Switch the parameter to int and fall back to node 0 when it is
NUMA_NO_NODE; node 0 is always present.&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;nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools&lt;/p&gt;
&lt;p&gt;nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the
numa_node forwarded from hctx-&amp;gt;numa_node by its single caller,
nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is
NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the
value becomes UINT_MAX and the index walks off the array (sized to
nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace
without a /dev node.&lt;/p&gt;
&lt;p&gt;Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffff889101603d38
  RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]
  Call Trace:
   nvme_init_hctx+0x10/0x20 [nvme]
   nvme_alloc_ns+0x9e/0xa10 [nvme_core]
   nvme_scan_ns+0x301/0x3b0 [nvme_core]
   nvme_scan_ns_async+0x23/0x30 [nvme_core]&lt;/p&gt;
&lt;p&gt;Switch the parameter to int and fall back to node 0 when it is
NUMA_NO_NODE; node 0 is always present.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-74383</guid>
    </item>
    <item>
      <title>GHSA-2x9w-pwqr-6m8q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2x9w-pwqr-6m8q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools&lt;/p&gt;
&lt;p&gt;nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the
numa_node forwarded from hctx-&amp;gt;numa_node by its single caller,
nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is
NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the
value becomes UINT_MAX and the index walks off the array (sized to
nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace
without a /dev node.&lt;/p&gt;
&lt;p&gt;Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffff889101603d38
  RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]
  Call Trace:
   nvme_init_hctx+0x10/0x20 [nvme]
   nvme_alloc_ns+0x9e/0xa10 [nvme_core]
   nvme_scan_ns+0x301/0x3b0 [nvme_core]
   nvme_scan_ns_async+0x23/0x30 [nvme_core]&lt;/p&gt;
&lt;p&gt;Switch the parameter to int and fall back to node 0 when it is
NUMA_NO_NODE; node 0 is always present.&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;nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools&lt;/p&gt;
&lt;p&gt;nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the
numa_node forwarded from hctx-&amp;gt;numa_node by its single caller,
nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is
NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the
value becomes UINT_MAX and the index walks off the array (sized to
nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace
without a /dev node.&lt;/p&gt;
&lt;p&gt;Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffff889101603d38
  RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]
  Call Trace:
   nvme_init_hctx+0x10/0x20 [nvme]
   nvme_alloc_ns+0x9e/0xa10 [nvme_core]
   nvme_scan_ns+0x301/0x3b0 [nvme_core]
   nvme_scan_ns_async+0x23/0x30 [nvme_core]&lt;/p&gt;
&lt;p&gt;Switch the parameter to int and fall back to node 0 when it is
NUMA_NO_NODE; node 0 is always present.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2x9w-pwqr-6m8q</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74383</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74383</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the numa_node forwarded from hctx-&amp;gt;numa_node by its single caller, nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the value becomes UINT_MAX and the index walks off the array (sized to nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace without a /dev node. Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:   BUG: unable to handle page fault for address: ffff889101603d38   RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]   Call Trace:    nvme_init_hctx+0x10/0x20 [nvme]    nvme_alloc_ns+0x9e/0xa10 [nvme_core]    nvme_scan_ns+0x301/0x3b0 [nvme_core]    nvme_scan_ns_async+0x23/0x30 [nvme_core] Switch the parameter to int and fall back to node 0 when it is NUMA_NO_NODE; node 0 is always present.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix out-of-bounds access in nvme_setup_descriptor_pools nvme_setup_descriptor_pools() indexes dev-&amp;gt;descriptor_pools[] using the numa_node forwarded from hctx-&amp;gt;numa_node by its single caller, nvme_init_hctx_common().  On a non-NUMA kernel hctx-&amp;gt;numa_node is NUMA_NO_NODE (-1).  Because the parameter was declared &amp;#39;unsigned&amp;#39;, the value becomes UINT_MAX and the index walks off the array (sized to nr_node_ids), faulting during nvme_alloc_ns() and leaving the namespace without a /dev node. Reproduces on any NVMe controller probed by a CONFIG_NUMA=n kernel:   BUG: unable to handle page fault for address: ffff889101603d38   RIP: 0010:nvme_init_hctx_common+0x5a/0x190 [nvme]   Call Trace:    nvme_init_hctx+0x10/0x20 [nvme]    nvme_alloc_ns+0x9e/0xa10 [nvme_core]    nvme_scan_ns+0x301/0x3b0 [nvme_core]    nvme_scan_ns_async+0x23/0x30 [nvme_core] Switch the parameter to int and fall back to node 0 when it is NUMA_NO_NODE; node 0 is always present.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74383</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>
