<?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 15:57:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-04217</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-04217</link>
      <description>bdu:2024-04217</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-04217</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-35887</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-35887</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-35887</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — 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-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-367447</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367447</link>
      <description>EUVD-2026-367447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367447</guid>
    </item>
    <item>
      <title>fkie_cve-2024-35887</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-35887</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ax25: fix use-after-free bugs caused by ax25_ds_del_timer&lt;/p&gt;
&lt;p&gt;When the ax25 device is detaching, the ax25_dev_device_down()
calls ax25_ds_del_timer() to cleanup the slave_timer. When
the timer handler is running, the ax25_ds_del_timer() that
calls del_timer() in it will return directly. As a result,
the use-after-free bugs could happen, one of the scenarios
is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)          |      (Thread 2)
                          | ax25_ds_timeout()
ax25_dev_device_down()    |
  ax25_ds_del_timer()     |
    del_timer()           |
  ax25_dev_put() //FREE   |
                          |  ax25_dev-&amp;gt; //USE&lt;/p&gt;
&lt;p&gt;In order to mitigate bugs, when the device is detaching, use
timer_shutdown_sync() to stop the timer.&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;ax25: fix use-after-free bugs caused by ax25_ds_del_timer&lt;/p&gt;
&lt;p&gt;When the ax25 device is detaching, the ax25_dev_device_down()
calls ax25_ds_del_timer() to cleanup the slave_timer. When
the timer handler is running, the ax25_ds_del_timer() that
calls del_timer() in it will return directly. As a result,
the use-after-free bugs could happen, one of the scenarios
is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)          |      (Thread 2)
                          | ax25_ds_timeout()
ax25_dev_device_down()    |
  ax25_ds_del_timer()     |
    del_timer()           |
  ax25_dev_put() //FREE   |
                          |  ax25_dev-&amp;gt; //USE&lt;/p&gt;
&lt;p&gt;In order to mitigate bugs, when the device is detaching, use
timer_shutdown_sync() to stop the timer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-35887</guid>
    </item>
    <item>
      <title>GHSA-x3w9-8c2f-ccvj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x3w9-8c2f-ccvj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ax25: fix use-after-free bugs caused by ax25_ds_del_timer&lt;/p&gt;
&lt;p&gt;When the ax25 device is detaching, the ax25_dev_device_down()
calls ax25_ds_del_timer() to cleanup the slave_timer. When
the timer handler is running, the ax25_ds_del_timer() that
calls del_timer() in it will return directly. As a result,
the use-after-free bugs could happen, one of the scenarios
is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)          |      (Thread 2)
                          | ax25_ds_timeout()
ax25_dev_device_down()    |
  ax25_ds_del_timer()     |
    del_timer()           |
  ax25_dev_put() //FREE   |
                          |  ax25_dev-&amp;gt; //USE&lt;/p&gt;
&lt;p&gt;In order to mitigate bugs, when the device is detaching, use
timer_shutdown_sync() to stop the timer.&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;ax25: fix use-after-free bugs caused by ax25_ds_del_timer&lt;/p&gt;
&lt;p&gt;When the ax25 device is detaching, the ax25_dev_device_down()
calls ax25_ds_del_timer() to cleanup the slave_timer. When
the timer handler is running, the ax25_ds_del_timer() that
calls del_timer() in it will return directly. As a result,
the use-after-free bugs could happen, one of the scenarios
is shown below:&lt;/p&gt;
&lt;p&gt;(Thread 1)          |      (Thread 2)
                          | ax25_ds_timeout()
ax25_dev_device_down()    |
  ax25_ds_del_timer()     |
    del_timer()           |
  ax25_dev_put() //FREE   |
                          |  ax25_dev-&amp;gt; //USE&lt;/p&gt;
&lt;p&gt;In order to mitigate bugs, when the device is detaching, use
timer_shutdown_sync() to stop the timer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x3w9-8c2f-ccvj</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-35887 — ax25: fix use-after-free bugs caused by ax25_ds_del_timer</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-35887</link>
      <description>msrc_CVE-2024-35887</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-35887</guid>
    </item>
    <item>
      <title>OESA-2024-1737 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1737</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;
afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server&#13;
&#13;
AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and
Linux&amp;amp;apos;s afs client switches between them when talking to a non-YFS server
if the read size, the file position or the sum of the two have the upper 32
bits set of the 64-bit value.&#13;
&#13;
This is a problem, however, since the file position and length fields of
FS.FetchData are *signed* 32-bit values.&#13;
&#13;
Fix this by capturing the capability bits obtained from the fileserver when
it&amp;amp;apos;s sent an FS.GetCapabilities RPC, rather than just discarding them, and
then picking out the VICED_CAPABILITY_64BITFILES flag.  This can then be
used to decide whether to use FS.FetchData or FS.FetchData64 - and also
FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to
switch on the parameter values.&#13;
&#13;
This capabilities flag could also be used to limit the maximum size of the
file, but all servers must be checked for that.&#13;
&#13;
Note that the issue does not exist with FS.StoreData - that uses *unsigned*
32-bit values.  It&amp;amp;apos;s also not a problem with Auristor servers as its
YFS.FetchData64 op uses unsigned 64-bit values.&#13;
&#13;
This can be tested by cloning a git repo through an OpenAFS client to an
OpenAFS server and then doing &amp;amp;quot;git status&amp;amp;quot; on it from a Linux afs
client[1].  Provided…&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;
afs: Fix corruption in reads at fpos 2G-4G from an OpenAFS server&#13;
&#13;
AFS-3 has two data fetch RPC variants, FS.FetchData and FS.FetchData64, and
Linux&amp;amp;apos;s afs client switches between them when talking to a non-YFS server
if the read size, the file position or the sum of the two have the upper 32
bits set of the 64-bit value.&#13;
&#13;
This is a problem, however, since the file position and length fields of
FS.FetchData are *signed* 32-bit values.&#13;
&#13;
Fix this by capturing the capability bits obtained from the fileserver when
it&amp;amp;apos;s sent an FS.GetCapabilities RPC, rather than just discarding them, and
then picking out the VICED_CAPABILITY_64BITFILES flag.  This can then be
used to decide whether to use FS.FetchData or FS.FetchData64 - and also
FS.StoreData or FS.StoreData64 - rather than using upper_32_bits() to
switch on the parameter values.&#13;
&#13;
This capabilities flag could also be used to limit the maximum size of the
file, but all servers must be checked for that.&#13;
&#13;
Note that the issue does not exist with FS.StoreData - that uses *unsigned*
32-bit values.  It&amp;amp;apos;s also not a problem with Auristor servers as its
YFS.FetchData64 op uses unsigned 64-bit values.&#13;
&#13;
This can be tested by cloning a git repo through an OpenAFS client to an
OpenAFS server and then doing &amp;amp;quot;git status&amp;amp;quot; on it from a Linux afs
client[1].  Provided…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1737</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1979-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1979-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:1979-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35887</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35887</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 177 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ax25: fix use-after-free bugs caused by ax25_ds_del_timer When the ax25 device is detaching, the ax25_dev_device_down() calls ax25_ds_del_timer() to cleanup the slave_timer. When the timer handler is running, the ax25_ds_del_timer() that calls del_timer() in it will return directly. As a result, the use-after-free bugs could happen, one of the scenarios is shown below:       (Thread 1)          |      (Thread 2)                           | ax25_ds_timeout() ax25_dev_device_down()    |   ax25_ds_del_timer()     |     del_timer()           |   ax25_dev_put() //FREE   |                           |  ax25_dev-&amp;gt; //USE In order to mitigate bugs, when the device is detaching, use timer_shutdown_sync() to stop the timer.&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 177 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ax25: fix use-after-free bugs caused by ax25_ds_del_timer When the ax25 device is detaching, the ax25_dev_device_down() calls ax25_ds_del_timer() to cleanup the slave_timer. When the timer handler is running, the ax25_ds_del_timer() that calls del_timer() in it will return directly. As a result, the use-after-free bugs could happen, one of the scenarios is shown below:       (Thread 1)          |      (Thread 2)                           | ax25_ds_timeout() ax25_dev_device_down()    |   ax25_ds_del_timer()     |     del_timer()           |   ax25_dev_put() //FREE   |                           |  ax25_dev-&amp;gt; //USE In order to mitigate bugs, when the device is detaching, use timer_shutdown_sync() to stop the timer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35887</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1188 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1188</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in 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 in 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-1188</guid>
    </item>
  </channel>
</rss>
