<?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://vulnerability.circl.lu</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, 10 Oct 2026 03:09:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80870 — drm/amdkfd: Validate CRIU-restored IDs before idr_alloc</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80870</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;drm/amdkfd: Validate CRIU-restored IDs before idr_alloc&lt;/p&gt;
&lt;p&gt;The KFD CRIU restore flow restores previously saved object IDs from
userspace.&lt;/p&gt;
&lt;p&gt;For event restore:&lt;/p&gt;
&lt;p&gt;kfd_criu_restore_event()
      -&amp;gt; create_signal_event() / create_other_event()
          -&amp;gt; allocate_event_notification_slot()
              -&amp;gt; idr_alloc(..., *restore_id, *restore_id + 1, ...)&lt;/p&gt;
&lt;p&gt;For BO restore:&lt;/p&gt;
&lt;p&gt;criu_restore_memory_of_gpu()
      -&amp;gt; idr_alloc(..., bo_priv-&amp;gt;idr_handle, ...)&lt;/p&gt;
&lt;p&gt;In both cases, the restored ID comes from userspace-provided CRIU data.&lt;/p&gt;
&lt;p&gt;idr_alloc() expects the ID range values to fit within signed int
limits. If a restored ID is larger than INT_MAX, it can trigger a WARN
in the IDR layer.&lt;/p&gt;
&lt;p&gt;A kernel WARN is undesirable because it prints a warning trace and may
cause a panic or reboot on systems with panic_on_warn enabled.&lt;/p&gt;
&lt;p&gt;Smatch reported these paths as allowing unchecked userspace values to
reach idr_alloc().&lt;/p&gt;
&lt;p&gt;Add INT_MAX validation before using restored IDs in:&lt;/p&gt;
&lt;p&gt;- kfd_criu_restore_event()
- criu_restore_memory_of_gpu()&lt;/p&gt;
&lt;p&gt;If the restored ID is invalid, return -EINVAL.&lt;/p&gt;
&lt;p&gt;This prevents invalid restore data from reaching the IDR layer and
avoids WARN-triggering paths, while keeping valid restore behavior
unchanged.&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;drm/amdkfd: Validate CRIU-restored IDs before idr_alloc&lt;/p&gt;
&lt;p&gt;The KFD CRIU restore flow restores previously saved object IDs from
userspace.&lt;/p&gt;
&lt;p&gt;For event restore:&lt;/p&gt;
&lt;p&gt;kfd_criu_restore_event()
      -&amp;gt; create_signal_event() / create_other_event()
          -&amp;gt; allocate_event_notification_slot()
              -&amp;gt; idr_alloc(..., *restore_id, *restore_id + 1, ...)&lt;/p&gt;
&lt;p&gt;For BO restore:&lt;/p&gt;
&lt;p&gt;criu_restore_memory_of_gpu()
      -&amp;gt; idr_alloc(..., bo_priv-&amp;gt;idr_handle, ...)&lt;/p&gt;
&lt;p&gt;In both cases, the restored ID comes from userspace-provided CRIU data.&lt;/p&gt;
&lt;p&gt;idr_alloc() expects the ID range values to fit within signed int
limits. If a restored ID is larger than INT_MAX, it can trigger a WARN
in the IDR layer.&lt;/p&gt;
&lt;p&gt;A kernel WARN is undesirable because it prints a warning trace and may
cause a panic or reboot on systems with panic_on_warn enabled.&lt;/p&gt;
&lt;p&gt;Smatch reported these paths as allowing unchecked userspace values to
reach idr_alloc().&lt;/p&gt;
&lt;p&gt;Add INT_MAX validation before using restored IDs in:&lt;/p&gt;
&lt;p&gt;- kfd_criu_restore_event()
- criu_restore_memory_of_gpu()&lt;/p&gt;
&lt;p&gt;If the restored ID is invalid, return -EINVAL.&lt;/p&gt;
&lt;p&gt;This prevents invalid restore data from reaching the IDR layer and
avoids WARN-triggering paths, while keeping valid restore behavior
unchanged.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80870</guid>
    </item>
    <item>
      <title>USN-8887-1 — linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://vulnerability.circl.lu/vuln/usn-8887-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly perform Reverse
Map Table (RMP) checks when the IOMMU accessed certain host buffers. A
local attacker with hypervisor access could possibly use this to trigger an
out-of-bounds condition and compromise the integrity of SEV-SNP guest
memory. (CVE-2023-20585)&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:
  - ARM64 architecture;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - DPLL subsystem;
  - EDAC drivers;
  - FireWire subsystem;
  - Arm Firmware Framework fo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly perform Reverse
Map Table (RMP) checks when the IOMMU accessed certain host buffers. A
local attacker with hypervisor access could possibly use this to trigger an
out-of-bounds condition and compromise the integrity of SEV-SNP guest
memory. (CVE-2023-20585)&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:
  - ARM64 architecture;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - DPLL subsystem;
  - EDAC drivers;
  - FireWire subsystem;
  - Arm Firmware Framework fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/usn-8887-1</guid>
    </item>
  </channel>
</rss>
