<?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>Sun, 11 Oct 2026 13:58:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74337 — bpf: Fix NMI/tracepoint re-entry deadlock on lru locks</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74337</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;bpf: Fix NMI/tracepoint re-entry deadlock on lru locks&lt;/p&gt;
&lt;p&gt;NMI and tracepoint BPF programs can re-enter the per-CPU or global
LRU lock that bpf_lru_pop_free()/push_free() already hold on the
same CPU, AA-deadlocking. Lockdep reports &amp;#34;inconsistent
{INITIAL USE} -&amp;gt; {IN-NMI}&amp;#34; on &amp;amp;l-&amp;gt;lock (syzbot c69a0a2c816716f1e0d5)
and &amp;#34;possible recursive locking detected&amp;#34; on &amp;amp;loc_l-&amp;gt;lock (syzbot
18b26edb69b2e19f3b33).&lt;/p&gt;
&lt;p&gt;Prior trylock and rqspinlock based fixes (see links) were nacked
because compromised on reliability.&lt;/p&gt;
&lt;p&gt;This patch converts every LRU lock site to rqspinlock_t and adds a
recovery path for some failure windows to avoid node leaks.&lt;/p&gt;
&lt;p&gt;Failure recovery:&lt;/p&gt;
&lt;p&gt;- *_pop_free top-level: return NULL; prealloc_lru_pop() already
   treats that as no-free-element (-ENOMEM).&lt;/p&gt;
&lt;p&gt;- Cross-CPU steal: skip the victim&amp;#39;s locked loc_l, try next CPU.&lt;/p&gt;
&lt;p&gt;- Post-steal local lock fail: publish stolen node to lockless
   per-CPU free_llist; next pop on this CPU picks it up.&lt;/p&gt;
&lt;p&gt;- push_free fail: mark node pending_free=1. __local_list_flush(),
   __local_list_pop_pending() reclaim the node from pending_list.
   __bpf_lru_list_shrink_inactive() reclaims the node from inactive
   list. Nodes from active list are reclaimed by __bpf_lru_list_shrink()
   or after __bpf_lru_list_rotate_active() demotes it to the inactive.&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;bpf: Fix NMI/tracepoint re-entry deadlock on lru locks&lt;/p&gt;
&lt;p&gt;NMI and tracepoint BPF programs can re-enter the per-CPU or global
LRU lock that bpf_lru_pop_free()/push_free() already hold on the
same CPU, AA-deadlocking. Lockdep reports &amp;#34;inconsistent
{INITIAL USE} -&amp;gt; {IN-NMI}&amp;#34; on &amp;amp;l-&amp;gt;lock (syzbot c69a0a2c816716f1e0d5)
and &amp;#34;possible recursive locking detected&amp;#34; on &amp;amp;loc_l-&amp;gt;lock (syzbot
18b26edb69b2e19f3b33).&lt;/p&gt;
&lt;p&gt;Prior trylock and rqspinlock based fixes (see links) were nacked
because compromised on reliability.&lt;/p&gt;
&lt;p&gt;This patch converts every LRU lock site to rqspinlock_t and adds a
recovery path for some failure windows to avoid node leaks.&lt;/p&gt;
&lt;p&gt;Failure recovery:&lt;/p&gt;
&lt;p&gt;- *_pop_free top-level: return NULL; prealloc_lru_pop() already
   treats that as no-free-element (-ENOMEM).&lt;/p&gt;
&lt;p&gt;- Cross-CPU steal: skip the victim&amp;#39;s locked loc_l, try next CPU.&lt;/p&gt;
&lt;p&gt;- Post-steal local lock fail: publish stolen node to lockless
   per-CPU free_llist; next pop on this CPU picks it up.&lt;/p&gt;
&lt;p&gt;- push_free fail: mark node pending_free=1. __local_list_flush(),
   __local_list_pop_pending() reclaim the node from pending_list.
   __bpf_lru_list_shrink_inactive() reclaims the node from inactive
   list. Nodes from active list are reclaimed by __bpf_lru_list_shrink()
   or after __bpf_lru_list_rotate_active() demotes it to the inactive.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74337</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>
