<?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 12:08:14 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-93173</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-93173</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-93173</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-371194</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-371194</link>
      <description>EUVD-2026-371194</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-371194</guid>
    </item>
    <item>
      <title>fkie_cve-2026-93173</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-93173</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks&lt;/p&gt;
&lt;p&gt;__bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs.
security_bpf_prog_free() called from there fires bpf_prog_free in softirq;
if a sleepable LSM prog is attached to that hook, might_fault() BUGs:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038
  preempt_count: 101, expected: 0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255
   bpf_trampoline_6442549705+0x53/0xd7
   security_bpf_prog_free+0xde/0x130 security/security.c:5465
   __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365
   rcu_do_batch kernel/rcu/tree.c:2617 [inline]
   handle_softirqs+0x236/0x800 kernel/softirq.c:622
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s
sleepability, not that of any attached observer.&lt;/p&gt;
&lt;p&gt;security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay
after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks
rather than move the call. Non-sleepable observers still run there.&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,lsm: Drop bpf_prog_free from sleepable_lsm_hooks&lt;/p&gt;
&lt;p&gt;__bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs.
security_bpf_prog_free() called from there fires bpf_prog_free in softirq;
if a sleepable LSM prog is attached to that hook, might_fault() BUGs:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038
  preempt_count: 101, expected: 0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255
   bpf_trampoline_6442549705+0x53/0xd7
   security_bpf_prog_free+0xde/0x130 security/security.c:5465
   __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365
   rcu_do_batch kernel/rcu/tree.c:2617 [inline]
   handle_softirqs+0x236/0x800 kernel/softirq.c:622
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s
sleepability, not that of any attached observer.&lt;/p&gt;
&lt;p&gt;security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay
after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks
rather than move the call. Non-sleepable observers still run there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-93173</guid>
    </item>
    <item>
      <title>GHSA-ggp7-x9rm-wrm3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ggp7-x9rm-wrm3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks&lt;/p&gt;
&lt;p&gt;__bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs.
security_bpf_prog_free() called from there fires bpf_prog_free in softirq;
if a sleepable LSM prog is attached to that hook, might_fault() BUGs:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038
  preempt_count: 101, expected: 0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255
   bpf_trampoline_6442549705+0x53/0xd7
   security_bpf_prog_free+0xde/0x130 security/security.c:5465
   __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365
   rcu_do_batch kernel/rcu/tree.c:2617 [inline]
   handle_softirqs+0x236/0x800 kernel/softirq.c:622
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s
sleepability, not that of any attached observer.&lt;/p&gt;
&lt;p&gt;security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay
after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks
rather than move the call. Non-sleepable observers still run there.&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,lsm: Drop bpf_prog_free from sleepable_lsm_hooks&lt;/p&gt;
&lt;p&gt;__bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs.
security_bpf_prog_free() called from there fires bpf_prog_free in softirq;
if a sleepable LSM prog is attached to that hook, might_fault() BUGs:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context
  in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038
  preempt_count: 101, expected: 0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255
   bpf_trampoline_6442549705+0x53/0xd7
   security_bpf_prog_free+0xde/0x130 security/security.c:5465
   __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365
   rcu_do_batch kernel/rcu/tree.c:2617 [inline]
   handle_softirqs+0x236/0x800 kernel/softirq.c:622
   &amp;lt;/IRQ&amp;gt;&lt;/p&gt;
&lt;p&gt;The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s
sleepability, not that of any attached observer.&lt;/p&gt;
&lt;p&gt;security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay
after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks
rather than move the call. Non-sleepable observers still run there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ggp7-x9rm-wrm3</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-93173</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-93173</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks __bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs. security_bpf_prog_free() called from there fires bpf_prog_free in softirq; if a sleepable LSM prog is attached to that hook, might_fault() BUGs:   BUG: sleeping function called from invalid context   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038   preempt_count: 101, expected: 0   Call Trace:    &amp;lt;IRQ&amp;gt;    __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255    bpf_trampoline_6442549705+0x53/0xd7    security_bpf_prog_free+0xde/0x130 security/security.c:5465    __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365    rcu_do_batch kernel/rcu/tree.c:2617 [inline]    handle_softirqs+0x236/0x800 kernel/softirq.c:622    &amp;lt;/IRQ&amp;gt; The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s sleepability, not that of any attached observer. security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks rather than move the call. Non-sleepable observers still run there.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf,lsm: Drop bpf_prog_free from sleepable_lsm_hooks __bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs. security_bpf_prog_free() called from there fires bpf_prog_free in softirq; if a sleepable LSM prog is attached to that hook, might_fault() BUGs:   BUG: sleeping function called from invalid context   in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038   preempt_count: 101, expected: 0   Call Trace:    &amp;lt;IRQ&amp;gt;    __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255    bpf_trampoline_6442549705+0x53/0xd7    security_bpf_prog_free+0xde/0x130 security/security.c:5465    __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365    rcu_do_batch kernel/rcu/tree.c:2617 [inline]    handle_softirqs+0x236/0x800 kernel/softirq.c:622    &amp;lt;/IRQ&amp;gt; The call_rcu/call_rcu_tasks_trace split reflects the freed program&amp;#39;s sleepability, not that of any attached observer. security_bpf_prog_free() also frees prog-&amp;gt;aux-&amp;gt;security, which has to stay after the grace period, so drop bpf_prog_free from sleepable_lsm_hooks rather than move the call. Non-sleepable observers still run there.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-93173</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3444 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444</guid>
    </item>
  </channel>
</rss>
