<?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>Sat, 03 Oct 2026 11:57:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74337</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-74337</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-74337</guid>
    </item>
    <item>
      <title>EUVD-2026-353828</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353828</link>
      <description>EUVD-2026-353828</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353828</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74337</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-74337</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-74337</guid>
    </item>
    <item>
      <title>GHSA-x3mj-vjph-62qr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x3mj-vjph-62qr</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-x3mj-vjph-62qr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74337</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74337</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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 &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). 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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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 &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). 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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74337</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
