<?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 06:07:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12224</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12224</link>
      <description>bdu:2025-12224</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12224</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56549</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56549</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-56549</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0047 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</link>
      <description>certfr-2025-avi-0047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0047</guid>
    </item>
    <item>
      <title>EUVD-2026-346464</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346464</link>
      <description>EUVD-2026-346464</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346464</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56549</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56549</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cachefiles: Fix NULL pointer dereference in object-&amp;gt;file&lt;/p&gt;
&lt;p&gt;At present, the object-&amp;gt;file has the NULL pointer dereference problem in
ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file
lifetime are inconsistent, and the user-space invocation to anon_fd uses
object-&amp;gt;file. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;[write fd]				[umount]
cachefiles_ondemand_fd_write_iter
				       fscache_cookie_state_machine
					 cachefiles_withdraw_cookie
  if (!file) return -ENOBUFS
					   cachefiles_clean_up_object
					     cachefiles_unmark_inode_in_use
					     fput(object-&amp;gt;file)
					     object-&amp;gt;file = NULL
  // file NULL pointer dereference!
  __cachefiles_write(..., file, ...)&lt;/p&gt;
&lt;p&gt;Fix this issue by add an additional reference count to the object-&amp;gt;file
before write/llseek, and decrement after it finished.&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;cachefiles: Fix NULL pointer dereference in object-&amp;gt;file&lt;/p&gt;
&lt;p&gt;At present, the object-&amp;gt;file has the NULL pointer dereference problem in
ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file
lifetime are inconsistent, and the user-space invocation to anon_fd uses
object-&amp;gt;file. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;[write fd]				[umount]
cachefiles_ondemand_fd_write_iter
				       fscache_cookie_state_machine
					 cachefiles_withdraw_cookie
  if (!file) return -ENOBUFS
					   cachefiles_clean_up_object
					     cachefiles_unmark_inode_in_use
					     fput(object-&amp;gt;file)
					     object-&amp;gt;file = NULL
  // file NULL pointer dereference!
  __cachefiles_write(..., file, ...)&lt;/p&gt;
&lt;p&gt;Fix this issue by add an additional reference count to the object-&amp;gt;file
before write/llseek, and decrement after it finished.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56549</guid>
    </item>
    <item>
      <title>GHSA-hm4v-3pg5-6f5c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hm4v-3pg5-6f5c</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;cachefiles: Fix NULL pointer dereference in object-&amp;gt;file&lt;/p&gt;
&lt;p&gt;At present, the object-&amp;gt;file has the NULL pointer dereference problem in
ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file
lifetime are inconsistent, and the user-space invocation to anon_fd uses
object-&amp;gt;file. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;[write fd]				[umount]
cachefiles_ondemand_fd_write_iter
				       fscache_cookie_state_machine
					 cachefiles_withdraw_cookie
  if (!file) return -ENOBUFS
					   cachefiles_clean_up_object
					     cachefiles_unmark_inode_in_use
					     fput(object-&amp;gt;file)
					     object-&amp;gt;file = NULL
  // file NULL pointer dereference!
  __cachefiles_write(..., file, ...)&lt;/p&gt;
&lt;p&gt;Fix this issue by add an additional reference count to the object-&amp;gt;file
before write/llseek, and decrement after it finished.&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;cachefiles: Fix NULL pointer dereference in object-&amp;gt;file&lt;/p&gt;
&lt;p&gt;At present, the object-&amp;gt;file has the NULL pointer dereference problem in
ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file
lifetime are inconsistent, and the user-space invocation to anon_fd uses
object-&amp;gt;file. Following is the process that triggers the issue:&lt;/p&gt;
&lt;p&gt;[write fd]				[umount]
cachefiles_ondemand_fd_write_iter
				       fscache_cookie_state_machine
					 cachefiles_withdraw_cookie
  if (!file) return -ENOBUFS
					   cachefiles_clean_up_object
					     cachefiles_unmark_inode_in_use
					     fput(object-&amp;gt;file)
					     object-&amp;gt;file = NULL
  // file NULL pointer dereference!
  __cachefiles_write(..., file, ...)&lt;/p&gt;
&lt;p&gt;Fix this issue by add an additional reference count to the object-&amp;gt;file
before write/llseek, and decrement after it finished.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hm4v-3pg5-6f5c</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-56549 — cachefiles: Fix NULL pointer dereference in object-&gt;file</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-56549</link>
      <description>msrc_CVE-2024-56549</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-56549</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>SUSE-SU-2025:0117-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0117-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:0117-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56549</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56549</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cachefiles: Fix NULL pointer dereference in object-&amp;gt;file At present, the object-&amp;gt;file has the NULL pointer dereference problem in ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file lifetime are inconsistent, and the user-space invocation to anon_fd uses object-&amp;gt;file. Following is the process that triggers the issue: 	  [write fd]				[umount] cachefiles_ondemand_fd_write_iter 				       fscache_cookie_state_machine 					 cachefiles_withdraw_cookie   if (!file) return -ENOBUFS 					   cachefiles_clean_up_object 					     cachefiles_unmark_inode_in_use 					     fput(object-&amp;gt;file) 					     object-&amp;gt;file = NULL   // file NULL pointer dereference!   __cachefiles_write(..., file, ...) Fix this issue by add an additional reference count to the object-&amp;gt;file before write/llseek, and decrement after it finished.&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: cachefiles: Fix NULL pointer dereference in object-&amp;gt;file At present, the object-&amp;gt;file has the NULL pointer dereference problem in ondemand-mode. The root cause is that the allocated fd and object-&amp;gt;file lifetime are inconsistent, and the user-space invocation to anon_fd uses object-&amp;gt;file. Following is the process that triggers the issue: 	  [write fd]				[umount] cachefiles_ondemand_fd_write_iter 				       fscache_cookie_state_machine 					 cachefiles_withdraw_cookie   if (!file) return -ENOBUFS 					   cachefiles_clean_up_object 					     cachefiles_unmark_inode_in_use 					     fput(object-&amp;gt;file) 					     object-&amp;gt;file = NULL   // file NULL pointer dereference!   __cachefiles_write(..., file, ...) Fix this issue by add an additional reference count to the object-&amp;gt;file before write/llseek, and decrement after it finished.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56549</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>
