<?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:10:36 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-03321</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03321</link>
      <description>bdu:2025-03321</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03321</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53131</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53131</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-53131</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0002 — 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-0002</link>
      <description>certfr-2025-avi-0002</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0002</guid>
    </item>
    <item>
      <title>EUVD-2026-313623</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313623</link>
      <description>EUVD-2026-313623</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313623</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53131</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53131</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;.&lt;/p&gt;
&lt;p&gt;This series fixes null pointer dereference bugs that occur when using
nilfs2 and two block-related tracepoints.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34;
tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a
NULL pointer dereference, or a general protection fault when KASAN is
enabled.&lt;/p&gt;
&lt;p&gt;This happens because since the tracepoint was added in touch_buffer(), it
references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the
buffer head has a pointer to a block_device structure.  In the current
implementation, the block_device structure is set after the function
returns to the caller.&lt;/p&gt;
&lt;p&gt;Here, touch_buffer() is used to mark the folio/page that owns the buffer
head as accessed, but the common search helper for folio/page used by the
caller function was optimized to mark the folio/page as accessed when it
was reimplemented a long time ago, eliminating the need to call
touch_buffer() here in the first place.&lt;/p&gt;
&lt;p&gt;So this solves the issue by eliminating the touch_buffer() call itself.&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;nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;.&lt;/p&gt;
&lt;p&gt;This series fixes null pointer dereference bugs that occur when using
nilfs2 and two block-related tracepoints.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34;
tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a
NULL pointer dereference, or a general protection fault when KASAN is
enabled.&lt;/p&gt;
&lt;p&gt;This happens because since the tracepoint was added in touch_buffer(), it
references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the
buffer head has a pointer to a block_device structure.  In the current
implementation, the block_device structure is set after the function
returns to the caller.&lt;/p&gt;
&lt;p&gt;Here, touch_buffer() is used to mark the folio/page that owns the buffer
head as accessed, but the common search helper for folio/page used by the
caller function was optimized to mark the folio/page as accessed when it
was reimplemented a long time ago, eliminating the need to call
touch_buffer() here in the first place.&lt;/p&gt;
&lt;p&gt;So this solves the issue by eliminating the touch_buffer() call itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53131</guid>
    </item>
    <item>
      <title>GHSA-p85v-4hp9-vq4r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p85v-4hp9-vq4r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;.&lt;/p&gt;
&lt;p&gt;This series fixes null pointer dereference bugs that occur when using
nilfs2 and two block-related tracepoints.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34;
tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a
NULL pointer dereference, or a general protection fault when KASAN is
enabled.&lt;/p&gt;
&lt;p&gt;This happens because since the tracepoint was added in touch_buffer(), it
references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the
buffer head has a pointer to a block_device structure.  In the current
implementation, the block_device structure is set after the function
returns to the caller.&lt;/p&gt;
&lt;p&gt;Here, touch_buffer() is used to mark the folio/page that owns the buffer
head as accessed, but the common search helper for folio/page used by the
caller function was optimized to mark the folio/page as accessed when it
was reimplemented a long time ago, eliminating the need to call
touch_buffer() here in the first place.&lt;/p&gt;
&lt;p&gt;So this solves the issue by eliminating the touch_buffer() call itself.&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;nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;.&lt;/p&gt;
&lt;p&gt;This series fixes null pointer dereference bugs that occur when using
nilfs2 and two block-related tracepoints.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34;
tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a
NULL pointer dereference, or a general protection fault when KASAN is
enabled.&lt;/p&gt;
&lt;p&gt;This happens because since the tracepoint was added in touch_buffer(), it
references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the
buffer head has a pointer to a block_device structure.  In the current
implementation, the block_device structure is set after the function
returns to the caller.&lt;/p&gt;
&lt;p&gt;Here, touch_buffer() is used to mark the folio/page that owns the buffer
head as accessed, but the common search helper for folio/page used by the
caller function was optimized to mark the folio/page as accessed when it
was reimplemented a long time ago, eliminating the need to call
touch_buffer() here in the first place.&lt;/p&gt;
&lt;p&gt;So this solves the issue by eliminating the touch_buffer() call itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p85v-4hp9-vq4r</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-53131 — nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-53131</link>
      <description>msrc_CVE-2024-53131</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-53131</guid>
    </item>
    <item>
      <title>OESA-2024-2570 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2570</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: SCO: Fix UAF on sco_sock_timeout  conn-&amp;amp;gt;sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn-&amp;amp;gt;sk is still valid by checking if it part of sco_sk_list.(CVE-2024-50125)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  be2net: fix potential memory leak in be_xmit()  The be_xmit() returns NETDEV_TX_OK without freeing skb in case of be_xmit_enqueue() fails, add dev_kfree_skb_any() to fix it.(CVE-2024-50167)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  net/sun3_82586: fix potential memory leak in sun3_82586_send_packet()  The sun3_82586_send_packet() returns NETDEV_TX_OK without freeing skb in case of skb-&amp;amp;gt;len being too long, add dev_kfree_skb() to fix it.(CVE-2024-50168)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_payload: sanitize offset and length before calling skb_checksum()  If access to offset + length is larger than the skbuff length, then skb_checksum() triggers BUG_ON().  skb_checksum() internally subtracts the length parameter while iterating over skbuff, BUG_ON(len) at the end of it checks that the expected length to be included in the checksum calculation is fully consumed.(CVE-2024-50251)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  net/sched: stop…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: SCO: Fix UAF on sco_sock_timeout  conn-&amp;amp;gt;sk maybe have been unlinked/freed while waiting for sco_conn_lock so this checks if the conn-&amp;amp;gt;sk is still valid by checking if it part of sco_sk_list.(CVE-2024-50125)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  be2net: fix potential memory leak in be_xmit()  The be_xmit() returns NETDEV_TX_OK without freeing skb in case of be_xmit_enqueue() fails, add dev_kfree_skb_any() to fix it.(CVE-2024-50167)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  net/sun3_82586: fix potential memory leak in sun3_82586_send_packet()  The sun3_82586_send_packet() returns NETDEV_TX_OK without freeing skb in case of skb-&amp;amp;gt;len being too long, add dev_kfree_skb() to fix it.(CVE-2024-50168)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_payload: sanitize offset and length before calling skb_checksum()  If access to offset + length is larger than the skbuff length, then skb_checksum() triggers BUG_ON().  skb_checksum() internally subtracts the length parameter while iterating over skbuff, BUG_ON(len) at the end of it checks that the expected length to be included in the checksum calculation is fully consumed.(CVE-2024-50251)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  net/sched: stop…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2570</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-53131</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53131</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;. This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints. This patch (of 2): It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34; tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled. This happens because since the tracepoint was added in touch_buffer(), it references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the buffer head has a pointer to a block_device structure.  In the current implementation, the block_device structure is set after the function returns to the caller. Here, touch_buffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touch_buffer() here in the first place. So this solves the issue by eliminating the touch_buffer() call itself.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint Patch series &amp;#34;nilfs2: fix null-ptr-deref bugs on block tracepoints&amp;#34;. This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints. This patch (of 2): It has been reported that when using &amp;#34;block:block_touch_buffer&amp;#34; tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled. This happens because since the tracepoint was added in touch_buffer(), it references the dev_t member bh-&amp;gt;b_bdev-&amp;gt;bd_dev regardless of whether the buffer head has a pointer to a block_device structure.  In the current implementation, the block_device structure is set after the function returns to the caller. Here, touch_buffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touch_buffer() here in the first place. So this solves the issue by eliminating the touch_buffer() call itself.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53131</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3608 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3608</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3608</guid>
    </item>
  </channel>
</rss>
