<?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 13:12:38 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03621</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03621</link>
      <description>bdu:2024-03621</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03621</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26689</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26689</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-26689</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>EUVD-2026-345487</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345487</link>
      <description>EUVD-2026-345487</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345487</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26689</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26689</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was
caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this
line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&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;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was
caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this
line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26689</guid>
    </item>
    <item>
      <title>GHSA-9xp8-8c5r-6wfh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9xp8-8c5r-6wfh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was
caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this
line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&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;ceph: prevent use-after-free in encode_cap_msg()&lt;/p&gt;
&lt;p&gt;In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was
caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This
implies before the refcount could be increment here, it was freed.&lt;/p&gt;
&lt;p&gt;In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this
line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race
occurred and resource was freed by the latter line before the former
line could increment it.&lt;/p&gt;
&lt;p&gt;encode_cap_msg() is called by __send_cap() and __send_cap() is called by
ceph_check_caps() after calling __prep_cap(). __prep_cap() is where
arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where
the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9xp8-8c5r-6wfh</guid>
    </item>
    <item>
      <title>gsd-2024-26689</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26689</link>
      <description>gsd-2024-26689</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26689</guid>
    </item>
    <item>
      <title>OESA-2024-1620 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1620</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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:&#13;
&#13;
firmware: arm_scmi: Harden accesses to the reset domains&#13;
&#13;
Accessing reset domains descriptors by the index upon the SCMI drivers
requests through the SCMI reset operations interface can potentially
lead to out-of-bound violations if the SCMI driver misbehave.&#13;
&#13;
Add an internal consistency check before any such domains descriptors
accesses.(CVE-2022-48655)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: hub: Guard against accesses to uninitialized BOS descriptors&#13;
&#13;
Many functions in drivers/usb/core/hub.c and drivers/usb/core/hub.h
access fields inside udev-&amp;amp;gt;bos without checking if it was allocated and
initialized. If usb_get_bos_descriptor() fails for whatever
reason, udev-&amp;amp;gt;bos will be NULL and those accesses will result in a
crash:&#13;
&#13;
BUG: kernel NULL pointer dereference, address: 0000000000000018
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 5 PID: 17818 Comm: kworker/5:1 Tainted: G W 5.15.108-18910-gab0e1cb584e1 #1 &amp;amp;lt;HASH:1f9e 1&amp;amp;gt;
Hardware name: Google Kindred/Kindred, BIOS Google_Kindred.12672.413.0 02/03/2021
Workqueue: usb_hub_wq hub_event
RIP: 0010:hub_port_reset+0x193/0x788
Code: 89 f7 e8 20 f7 15 00 48 8b 43 08 80 b8 96 03 00 00 03 75 36 0f b7 88 92 03 00 00 81 f9 10 03 00 00 72 27 48 8b 80 a8 03 00 00 &amp;amp;lt;48&amp;amp;gt; 83 78 18 00 74 19 48 89 df 48 8b 75 b0 ba 02 00 00 00 4c 89…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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:&#13;
&#13;
firmware: arm_scmi: Harden accesses to the reset domains&#13;
&#13;
Accessing reset domains descriptors by the index upon the SCMI drivers
requests through the SCMI reset operations interface can potentially
lead to out-of-bound violations if the SCMI driver misbehave.&#13;
&#13;
Add an internal consistency check before any such domains descriptors
accesses.(CVE-2022-48655)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: hub: Guard against accesses to uninitialized BOS descriptors&#13;
&#13;
Many functions in drivers/usb/core/hub.c and drivers/usb/core/hub.h
access fields inside udev-&amp;amp;gt;bos without checking if it was allocated and
initialized. If usb_get_bos_descriptor() fails for whatever
reason, udev-&amp;amp;gt;bos will be NULL and those accesses will result in a
crash:&#13;
&#13;
BUG: kernel NULL pointer dereference, address: 0000000000000018
PGD 0 P4D 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 5 PID: 17818 Comm: kworker/5:1 Tainted: G W 5.15.108-18910-gab0e1cb584e1 #1 &amp;amp;lt;HASH:1f9e 1&amp;amp;gt;
Hardware name: Google Kindred/Kindred, BIOS Google_Kindred.12672.413.0 02/03/2021
Workqueue: usb_hub_wq hub_event
RIP: 0010:hub_port_reset+0x193/0x788
Code: 89 f7 e8 20 f7 15 00 48 8b 43 08 80 b8 96 03 00 00 03 75 36 0f b7 88 92 03 00 00 81 f9 10 03 00 00 72 27 48 8b 80 a8 03 00 00 &amp;amp;lt;48&amp;amp;gt; 83 78 18 00 74 19 48 89 df 48 8b 75 b0 ba 02 00 00 00 4c 89…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1620</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1490-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1490-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-2024:1490-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26689</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26689</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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: prevent use-after-free in encode_cap_msg() In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This implies before the refcount could be increment here, it was freed. In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race occurred and resource was freed by the latter line before the former line could increment it. encode_cap_msg() is called by __send_cap() and __send_cap() is called by ceph_check_caps() after calling __prep_cap(). __prep_cap() is where arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&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 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ceph: prevent use-after-free in encode_cap_msg() In fs/ceph/caps.c, in encode_cap_msg(), &amp;#34;use after free&amp;#34; error was caught by KASAN at this line - &amp;#39;ceph_buffer_get(arg-&amp;gt;xattr_buf);&amp;#39;. This implies before the refcount could be increment here, it was freed. In same file, in &amp;#34;handle_cap_grant()&amp;#34; refcount is decremented by this line - &amp;#39;ceph_buffer_put(ci-&amp;gt;i_xattrs.blob);&amp;#39;. It appears that a race occurred and resource was freed by the latter line before the former line could increment it. encode_cap_msg() is called by __send_cap() and __send_cap() is called by ceph_check_caps() after calling __prep_cap(). __prep_cap() is where arg-&amp;gt;xattr_buf is assigned to ci-&amp;gt;i_xattrs.blob. This is the spot where the refcount must be increased to prevent &amp;#34;use after free&amp;#34; error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26689</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0773 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0773</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, seine Privilegien eskalieren oder einen nicht näher spezifizierten 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, seine Privilegien eskalieren oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0773</guid>
    </item>
  </channel>
</rss>
