<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T12:40:48.809191+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-74337</id>
    <title>BELL-CVE-2026-74337</title>
    <updated>2026-10-03T12:40:48.825993+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-74337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-353828</id>
    <title>EUVD-2026-353828</title>
    <updated>2026-10-03T12:40:48.826046+00:00</updated>
    <content>EUVD-2026-353828</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-353828"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74337</id>
    <title>fkie_cve-2026-74337</title>
    <updated>2026-10-03T12:40:48.826061+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Fix NMI/tracepoint re-entry deadlock on lru locks</p>
<p>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 "inconsistent
{INITIAL USE} -&gt; {IN-NMI}" on &amp;l-&gt;lock (syzbot c69a0a2c816716f1e0d5)
and "possible recursive locking detected" on &amp;loc_l-&gt;lock (syzbot
18b26edb69b2e19f3b33).</p>
<p>Prior trylock and rqspinlock based fixes (see links) were nacked
because compromised on reliability.</p>
<p>This patch converts every LRU lock site to rqspinlock_t and adds a
recovery path for some failure windows to avoid node leaks.</p>
<p>Failure recovery:</p>
<p>- *_pop_free top-level: return NULL; prealloc_lru_pop() already
   treats that as no-free-element (-ENOMEM).</p>
<p>- Cross-CPU steal: skip the victim's locked loc_l, try next CPU.</p>
<p>- Post-steal local lock fail: publish stolen node to lockless
   per-CPU free_llist; next pop on this CPU picks it up.</p>
<p>- 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-74337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-x3mj-vjph-62qr</id>
    <title>GHSA-x3mj-vjph-62qr</title>
    <updated>2026-10-03T12:40:48.826101+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Fix NMI/tracepoint re-entry deadlock on lru locks</p>
<p>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 "inconsistent
{INITIAL USE} -&gt; {IN-NMI}" on &amp;l-&gt;lock (syzbot c69a0a2c816716f1e0d5)
and "possible recursive locking detected" on &amp;loc_l-&gt;lock (syzbot
18b26edb69b2e19f3b33).</p>
<p>Prior trylock and rqspinlock based fixes (see links) were nacked
because compromised on reliability.</p>
<p>This patch converts every LRU lock site to rqspinlock_t and adds a
recovery path for some failure windows to avoid node leaks.</p>
<p>Failure recovery:</p>
<p>- *_pop_free top-level: return NULL; prealloc_lru_pop() already
   treats that as no-free-element (-ENOMEM).</p>
<p>- Cross-CPU steal: skip the victim's locked loc_l, try next CPU.</p>
<p>- Post-steal local lock fail: publish stolen node to lockless
   per-CPU free_llist; next pop on this CPU picks it up.</p>
<p>- 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-x3mj-vjph-62qr"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74337</id>
    <title>UBUNTU-CVE-2026-74337</title>
    <updated>2026-10-03T12:40:48.826130+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bpf: Fix NMI/tracepoint re-entry deadlock on lru locks 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 "inconsistent {INITIAL USE} -&gt; {IN-NMI}" on &amp;l-&gt;lock (syzbot c69a0a2c816716f1e0d5) and "possible recursive locking detected" on &amp;loc_l-&gt;lock (syzbot 18b26edb69b2e19f3b33). Prior trylock and rqspinlock based fixes (see links) were nacked because compromised on reliability. This patch converts every LRU lock site to rqspinlock_t and adds a recovery path for some failure windows to avoid node leaks. Failure recovery:  - *_pop_free top-level: return NULL; prealloc_lru_pop() already    treats that as no-free-element (-ENOMEM).  - Cross-CPU steal: skip the victim's locked loc_l, try next CPU.  - Post-steal local lock fail: publish stolen node to lockless    per-CPU free_llist; next pop on this CPU picks it up.  - 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74337"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</id>
    <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T12:40:48.826467+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852"/>
  </entry>
</feed>
