<?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>Fri, 02 Oct 2026 23:30:26 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14438</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-14438</link>
      <description>bdu:2026-14438</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-14438</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-338742</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338742</link>
      <description>EUVD-2026-338742</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338742</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64071</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64071</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvme-pci: fix use-after-free in nvme_free_host_mem()&lt;/p&gt;
&lt;p&gt;nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous()
but never clears the pointer afterward.  This leads to a use-after-free
if nvme_free_host_mem() is called twice in the same error path.&lt;/p&gt;
&lt;p&gt;This can happen during nvme_probe() when nvme_setup_host_mem() succeeds
in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem()
fails with an I/O error:&lt;/p&gt;
&lt;p&gt;nvme_setup_host_mem()
    nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt
    nvme_set_host_mem()            -&amp;gt; fails with -EIO
    nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it
    return error&lt;/p&gt;
&lt;p&gt;nvme_probe() error path:
    nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free&lt;/p&gt;
&lt;p&gt;The second call dereferences the freed sgt, causing a NULL pointer
dereference in iommu_dma_free_noncontiguous() when it accesses
sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed).&lt;/p&gt;
&lt;p&gt;This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC
Envoy Express behind a Dell WD22TB4 dock) where the device intermittently
returns I/O errors during HMB setup due to PCIe link instability.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
 RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dma_free_noncontiguous+0x3b/0x130
  nvme_free_host_mem+0x30/0xf0 [nvme]
  nvme_probe.cold+0xcc/0x275 [nvme]
  local_pci_pro…&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 use-after-free in nvme_free_host_mem()&lt;/p&gt;
&lt;p&gt;nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous()
but never clears the pointer afterward.  This leads to a use-after-free
if nvme_free_host_mem() is called twice in the same error path.&lt;/p&gt;
&lt;p&gt;This can happen during nvme_probe() when nvme_setup_host_mem() succeeds
in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem()
fails with an I/O error:&lt;/p&gt;
&lt;p&gt;nvme_setup_host_mem()
    nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt
    nvme_set_host_mem()            -&amp;gt; fails with -EIO
    nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it
    return error&lt;/p&gt;
&lt;p&gt;nvme_probe() error path:
    nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free&lt;/p&gt;
&lt;p&gt;The second call dereferences the freed sgt, causing a NULL pointer
dereference in iommu_dma_free_noncontiguous() when it accesses
sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed).&lt;/p&gt;
&lt;p&gt;This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC
Envoy Express behind a Dell WD22TB4 dock) where the device intermittently
returns I/O errors during HMB setup due to PCIe link instability.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
 RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dma_free_noncontiguous+0x3b/0x130
  nvme_free_host_mem+0x30/0xf0 [nvme]
  nvme_probe.cold+0xcc/0x275 [nvme]
  local_pci_pro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64071</guid>
    </item>
    <item>
      <title>GHSA-g774-9rm3-mcq6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g774-9rm3-mcq6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvme-pci: fix use-after-free in nvme_free_host_mem()&lt;/p&gt;
&lt;p&gt;nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous()
but never clears the pointer afterward.  This leads to a use-after-free
if nvme_free_host_mem() is called twice in the same error path.&lt;/p&gt;
&lt;p&gt;This can happen during nvme_probe() when nvme_setup_host_mem() succeeds
in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem()
fails with an I/O error:&lt;/p&gt;
&lt;p&gt;nvme_setup_host_mem()
    nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt
    nvme_set_host_mem()            -&amp;gt; fails with -EIO
    nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it
    return error&lt;/p&gt;
&lt;p&gt;nvme_probe() error path:
    nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free&lt;/p&gt;
&lt;p&gt;The second call dereferences the freed sgt, causing a NULL pointer
dereference in iommu_dma_free_noncontiguous() when it accesses
sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed).&lt;/p&gt;
&lt;p&gt;This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC
Envoy Express behind a Dell WD22TB4 dock) where the device intermittently
returns I/O errors during HMB setup due to PCIe link instability.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
 RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dma_free_noncontiguous+0x3b/0x130
  nvme_free_host_mem+0x30/0xf0 [nvme]
  nvme_probe.cold+0xcc/0x275 [nvme]
  local_pci_pro…&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 use-after-free in nvme_free_host_mem()&lt;/p&gt;
&lt;p&gt;nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous()
but never clears the pointer afterward.  This leads to a use-after-free
if nvme_free_host_mem() is called twice in the same error path.&lt;/p&gt;
&lt;p&gt;This can happen during nvme_probe() when nvme_setup_host_mem() succeeds
in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem()
fails with an I/O error:&lt;/p&gt;
&lt;p&gt;nvme_setup_host_mem()
    nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt
    nvme_set_host_mem()            -&amp;gt; fails with -EIO
    nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it
    return error&lt;/p&gt;
&lt;p&gt;nvme_probe() error path:
    nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free&lt;/p&gt;
&lt;p&gt;The second call dereferences the freed sgt, causing a NULL pointer
dereference in iommu_dma_free_noncontiguous() when it accesses
sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed).&lt;/p&gt;
&lt;p&gt;This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC
Envoy Express behind a Dell WD22TB4 dock) where the device intermittently
returns I/O errors during HMB setup due to PCIe link instability.&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000010
 RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dma_free_noncontiguous+0x3b/0x130
  nvme_free_host_mem+0x30/0xf0 [nvme]
  nvme_probe.cold+0xcc/0x275 [nvme]
  local_pci_pro…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g774-9rm3-mcq6</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-64071</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64071</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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix use-after-free in nvme_free_host_mem() nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous() but never clears the pointer afterward.  This leads to a use-after-free if nvme_free_host_mem() is called twice in the same error path. This can happen during nvme_probe() when nvme_setup_host_mem() succeeds in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem() fails with an I/O error:   nvme_setup_host_mem()     nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt     nvme_set_host_mem()            -&amp;gt; fails with -EIO     nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it     return error   nvme_probe() error path:     nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free The second call dereferences the freed sgt, causing a NULL pointer dereference in iommu_dma_free_noncontiguous() when it accesses sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed). This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC Envoy Express behind a Dell WD22TB4 dock) where the device intermittently returns I/O errors during HMB setup due to PCIe link instability.  BUG: kernel NULL pointer dereference, address: 0000000000000010  RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80  Call Trace:   &amp;lt;TASK&amp;gt;   dma_free_noncontiguous+0x3b/0x130   nvme_free_host_mem+0x30/0xf0 [nvme]   nvme_probe.cold+0xcc/0x275 [nvme]   local_pci_probe+0x43/…&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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix use-after-free in nvme_free_host_mem() nvme_free_host_mem() frees dev-&amp;gt;hmb_sgt via dma_free_noncontiguous() but never clears the pointer afterward.  This leads to a use-after-free if nvme_free_host_mem() is called twice in the same error path. This can happen during nvme_probe() when nvme_setup_host_mem() succeeds in allocating the HMB (setting dev-&amp;gt;hmb_sgt) but nvme_set_host_mem() fails with an I/O error:   nvme_setup_host_mem()     nvme_alloc_host_mem_single()   -&amp;gt; sets dev-&amp;gt;hmb_sgt     nvme_set_host_mem()            -&amp;gt; fails with -EIO     nvme_free_host_mem()           -&amp;gt; frees hmb_sgt, but does NOT NULL it     return error   nvme_probe() error path:     nvme_free_host_mem()           -&amp;gt; dev-&amp;gt;hmb_sgt is stale, use-after-free The second call dereferences the freed sgt, causing a NULL pointer dereference in iommu_dma_free_noncontiguous() when it accesses sgt-&amp;gt;sgl-&amp;gt;dma_address (the backing memory has been freed and zeroed). This is reproducible on Thunderbolt-attached NVMe devices (e.g., OWC Envoy Express behind a Dell WD22TB4 dock) where the device intermittently returns I/O errors during HMB setup due to PCIe link instability.  BUG: kernel NULL pointer dereference, address: 0000000000000010  RIP: 0010:iommu_dma_free_noncontiguous+0x22/0x80  Call Trace:   &amp;lt;TASK&amp;gt;   dma_free_noncontiguous+0x3b/0x130   nvme_free_host_mem+0x30/0xf0 [nvme]   nvme_probe.cold+0xcc/0x275 [nvme]   local_pci_probe+0x43/…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64071</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&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 Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
