<?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>Mon, 12 Oct 2026 16:15:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64071 — nvme-pci: fix use-after-free in nvme_free_host_mem()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-64071</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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/cve-2026-64071</guid>
    </item>
    <item>
      <title>USN-8593-1 — linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8593-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - x86 platform drivers;
  - PSP security protocol;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - DPLL subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FWCTL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD Zen 2 processors did not properly isolate
shared resources in the operation cache. A local attacker could possibly
use this issue to corrupt instructions executed at a higher privilege
level, resulting in privilege escalation. (CVE-2025-54518)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - x86 platform drivers;
  - PSP security protocol;
  - ARM32 architecture;
  - ARM64 architecture;
  - MIPS architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Intel NPU Driver;
  - Compute Acceleration Framework;
  - ACPI drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - DRBD Distributed Replicated Block Device drivers;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - Character device driver;
  - Clock framework and drivers;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - DPLL subsystem;
  - EDAC drivers;
  - Arm Firmware Framework for ARMv8-A(FFA);
  - EFI core;
  - FWCTL subsystem;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - I…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8593-1</guid>
    </item>
  </channel>
</rss>
