<?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>Sun, 04 Oct 2026 05:21:56 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07802</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07802</link>
      <description>bdu:2025-07802</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07802</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56585</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56585</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-2024-56585</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0184 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0184</link>
      <description>certfr-2025-avi-0184</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0184</guid>
    </item>
    <item>
      <title>EUVD-2026-313741</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313741</link>
      <description>EUVD-2026-313741</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313741</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56585</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56585</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&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;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56585</guid>
    </item>
    <item>
      <title>GHSA-2ggg-8w3g-3x2x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2ggg-8w3g-3x2x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&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;LoongArch: Fix sleeping in atomic context for PREEMPT_RT&lt;/p&gt;
&lt;p&gt;Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in
setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC
for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get
a &amp;#34;sleeping in atomic context&amp;#34; error:&lt;/p&gt;
&lt;p&gt;[    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
[    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1
[    0.372268] preempt_count: 1, expected: 0
[    0.372270] RCU nest depth: 1, expected: 1
[    0.372272] 3 locks held by swapper/1/0:
[    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60
[    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140
[    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0
[    0.372314] irq event stamp: 0
[    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0
[    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0
[    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891
[    0.372346] Hardware name: Loongson Loongson…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2ggg-8w3g-3x2x</guid>
    </item>
    <item>
      <title>OESA-2025-1078 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1078</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new&lt;/p&gt;
&lt;p&gt;This patch enhances error handling in scenarios with RTS (Request to
Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
backtraces with a new error handling method. This provides clearer error
messages and allows for the early termination of problematic sessions.
Previously, sessions were only released at the end of j1939_xtp_rx_rts().&lt;/p&gt;
&lt;p&gt;Potentially this could be reproduced with something like:
testj1939 -r vcan0:0x80 &amp;amp;amp;
while true; do
	# send first RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send second RTS
	cansend vcan0 18EC8090#1014000303002301;
	# send abort
	cansend vcan0 18EC8090#ff00000000002301;
done(CVE-2023-52887)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix slab-use-after-free in l2cap_connect()&lt;/p&gt;
&lt;p&gt;Extend a critical section to prevent chan from early freeing.
Also make the l2cap_connect() return type void. Nothing is using the
returned value but it is ugly to return a potentially freed pointer.
Making it void will help with backports because earlier kernels did use
the return value. Now the compile will break for kernels where this
patch is not a complete fix.&lt;/p&gt;
&lt;p&gt;Call stack summary:&lt;/p&gt;
&lt;p&gt;[use]
l2cap_bredr_sig_cmd
  l2cap_connect
  ┌ mutex_lock(&amp;amp;amp;c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1078</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56585</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56585</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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix sleeping in atomic context for PREEMPT_RT Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get a &amp;#34;sleeping in atomic context&amp;#34; error: [    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [    0.372268] preempt_count: 1, expected: 0 [    0.372270] RCU nest depth: 1, expected: 1 [    0.372272] 3 locks held by swapper/1/0: [    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60 [    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140 [    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0 [    0.372314] irq event stamp: 0 [    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0 [    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0 [    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0 [    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0 [    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891 [    0.372346] Hardware name: Loongson Loongson-3A…&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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix sleeping in atomic context for PREEMPT_RT Commit bab1c299f3945ffe79 (&amp;#34;LoongArch: Fix sleeping in atomic context in setup_tlb_handler()&amp;#34;) changes the gfp flag from GFP_KERNEL to GFP_ATOMIC for alloc_pages_node(). However, for PREEMPT_RT kernels we can still get a &amp;#34;sleeping in atomic context&amp;#34; error: [    0.372259] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [    0.372266] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [    0.372268] preempt_count: 1, expected: 0 [    0.372270] RCU nest depth: 1, expected: 1 [    0.372272] 3 locks held by swapper/1/0: [    0.372274]  #0: 900000000c9f5e60 (&amp;amp;pcp-&amp;gt;lock){+.+.}-{3:3}, at: get_page_from_freelist+0x524/0x1c60 [    0.372294]  #1: 90000000087013b8 (rcu_read_lock){....}-{1:3}, at: rt_spin_trylock+0x50/0x140 [    0.372305]  #2: 900000047fffd388 (&amp;amp;zone-&amp;gt;lock){+.+.}-{3:3}, at: __rmqueue_pcplist+0x30c/0xea0 [    0.372314] irq event stamp: 0 [    0.372316] hardirqs last  enabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0 [    0.372322] hardirqs last disabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0 [    0.372329] softirqs last  enabled at (0): [&amp;lt;9000000005947320&amp;gt;] copy_process+0x9c0/0x26e0 [    0.372335] softirqs last disabled at (0): [&amp;lt;0000000000000000&amp;gt;] 0x0 [    0.372341] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7+ #1891 [    0.372346] Hardware name: Loongson Loongson-3A…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56585</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
