<?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>Fri, 02 Oct 2026 16:30:17 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-16269</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-16269</link>
      <description>bdu:2025-16269</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-16269</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53520</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53520</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-53520</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>EUVD-2026-345235</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345235</link>
      <description>EUVD-2026-345235</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345235</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53520</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53520</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: Fix hci_suspend_sync crash&lt;/p&gt;
&lt;p&gt;If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier
may still be accessing it, it can cause the program to crash.
Here&amp;#39;s the call trace:
  &amp;lt;4&amp;gt;[102152.653246] Call Trace:
  &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]
  &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]
  &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]
  &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b
  &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69
  &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39
  &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c
  &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5
  &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173
  &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2
  &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f
  &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109
  &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d
  &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb
  &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194
  &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1&lt;/p&gt;
&lt;p&gt;This patch holds the reference count of the hci_dev object while
processing it in hci_suspend_notifier to avoid potential crash
caused by the race condition.&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;Bluetooth: Fix hci_suspend_sync crash&lt;/p&gt;
&lt;p&gt;If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier
may still be accessing it, it can cause the program to crash.
Here&amp;#39;s the call trace:
  &amp;lt;4&amp;gt;[102152.653246] Call Trace:
  &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]
  &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]
  &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]
  &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b
  &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69
  &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39
  &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c
  &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5
  &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173
  &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2
  &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f
  &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109
  &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d
  &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb
  &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194
  &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1&lt;/p&gt;
&lt;p&gt;This patch holds the reference count of the hci_dev object while
processing it in hci_suspend_notifier to avoid potential crash
caused by the race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53520</guid>
    </item>
    <item>
      <title>GHSA-fxhr-ffpx-g953</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fxhr-ffpx-g953</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: Fix hci_suspend_sync crash&lt;/p&gt;
&lt;p&gt;If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier
may still be accessing it, it can cause the program to crash.
Here&amp;#39;s the call trace:
  &amp;lt;4&amp;gt;[102152.653246] Call Trace:
  &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]
  &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]
  &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]
  &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b
  &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69
  &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39
  &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c
  &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5
  &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173
  &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2
  &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f
  &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109
  &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d
  &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb
  &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194
  &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1&lt;/p&gt;
&lt;p&gt;This patch holds the reference count of the hci_dev object while
processing it in hci_suspend_notifier to avoid potential crash
caused by the race condition.&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;Bluetooth: Fix hci_suspend_sync crash&lt;/p&gt;
&lt;p&gt;If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier
may still be accessing it, it can cause the program to crash.
Here&amp;#39;s the call trace:
  &amp;lt;4&amp;gt;[102152.653246] Call Trace:
  &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]
  &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]
  &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]
  &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b
  &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69
  &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39
  &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c
  &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5
  &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173
  &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2
  &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f
  &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109
  &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d
  &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb
  &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194
  &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1&lt;/p&gt;
&lt;p&gt;This patch holds the reference count of the hci_dev object while
processing it in hci_suspend_notifier to avoid potential crash
caused by the race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fxhr-ffpx-g953</guid>
    </item>
    <item>
      <title>OESA-2025-2800 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2800</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;ext4: update s_journal_inum if it changes after journal replay&lt;/p&gt;
&lt;p&gt;When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.(CVE-2023-53091)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: Fix nexthop hash size&lt;/p&gt;
&lt;p&gt;The nexthop code expects a 31 bit hash, such as what is returned by
fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash
returned by skb_get_hash() can lead to problems related to the fact that
&amp;amp;apos;int hash&amp;amp;apos; is a negative number when the MSB is set.&lt;/p&gt;
&lt;p&gt;In the case of hash threshold nexthop groups, nexthop_select_path_hthr()
will disproportionately select the first nexthop group entry. In the case
of resilient nexthop groups, nexthop_select_path_res() may do an out of
bounds access in nh_buckets[], for example:
    hash = -912054133
    num_nh_buckets = 2
    bucket_index = 65535&lt;/p&gt;
&lt;p&gt;which leads to the following panic:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc9000…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;ext4: update s_journal_inum if it changes after journal replay&lt;/p&gt;
&lt;p&gt;When mounting a crafted ext4 image, s_journal_inum may change after journal
replay, which is obviously unreasonable because we have successfully loaded
and replayed the journal through the old s_journal_inum. And the new
s_journal_inum bypasses some of the checks in ext4_get_journal(), which
may trigger a null pointer dereference problem. So if s_journal_inum
changes after the journal replay, we ignore the change, and rewrite the
current journal_inum to the superblock.(CVE-2023-53091)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: Fix nexthop hash size&lt;/p&gt;
&lt;p&gt;The nexthop code expects a 31 bit hash, such as what is returned by
fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash
returned by skb_get_hash() can lead to problems related to the fact that
&amp;amp;apos;int hash&amp;amp;apos; is a negative number when the MSB is set.&lt;/p&gt;
&lt;p&gt;In the case of hash threshold nexthop groups, nexthop_select_path_hthr()
will disproportionately select the first nexthop group entry. In the case
of resilient nexthop groups, nexthop_select_path_res() may do an out of
bounds access in nh_buckets[], for example:
    hash = -912054133
    num_nh_buckets = 2
    bucket_index = 65535&lt;/p&gt;
&lt;p&gt;which leads to the following panic:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffc9000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2800</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53520</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53520</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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hci_suspend_sync crash If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier may still be accessing it, it can cause the program to crash. Here&amp;#39;s the call trace:   &amp;lt;4&amp;gt;[102152.653246] Call Trace:   &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]   &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]   &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]   &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b   &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69   &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39   &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c   &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5   &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173   &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2   &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f   &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109   &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d   &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb   &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194   &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1 This patch holds the reference count of the hci_dev object while processing it in hci_suspend_notifier to avoid potential crash caused by the race condition.&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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hci_suspend_sync crash If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier may still be accessing it, it can cause the program to crash. Here&amp;#39;s the call trace:   &amp;lt;4&amp;gt;[102152.653246] Call Trace:   &amp;lt;4&amp;gt;[102152.653254]  hci_suspend_sync+0x109/0x301 [bluetooth]   &amp;lt;4&amp;gt;[102152.653259]  hci_suspend_dev+0x78/0xcd [bluetooth]   &amp;lt;4&amp;gt;[102152.653263]  hci_suspend_notifier+0x42/0x7a [bluetooth]   &amp;lt;4&amp;gt;[102152.653268]  notifier_call_chain+0x43/0x6b   &amp;lt;4&amp;gt;[102152.653271]  __blocking_notifier_call_chain+0x48/0x69   &amp;lt;4&amp;gt;[102152.653273]  __pm_notifier_call_chain+0x22/0x39   &amp;lt;4&amp;gt;[102152.653276]  pm_suspend+0x287/0x57c   &amp;lt;4&amp;gt;[102152.653278]  state_store+0xae/0xe5   &amp;lt;4&amp;gt;[102152.653281]  kernfs_fop_write+0x109/0x173   &amp;lt;4&amp;gt;[102152.653284]  __vfs_write+0x16f/0x1a2   &amp;lt;4&amp;gt;[102152.653287]  ? selinux_file_permission+0xca/0x16f   &amp;lt;4&amp;gt;[102152.653289]  ? security_file_permission+0x36/0x109   &amp;lt;4&amp;gt;[102152.653291]  vfs_write+0x114/0x21d   &amp;lt;4&amp;gt;[102152.653293]  __x64_sys_write+0x7b/0xdb   &amp;lt;4&amp;gt;[102152.653296]  do_syscall_64+0x59/0x194   &amp;lt;4&amp;gt;[102152.653299]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1 This patch holds the reference count of the hci_dev object while processing it in hci_suspend_notifier to avoid potential crash caused by the race condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53520</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
