<?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 17:15:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15084</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15084</link>
      <description>bdu:2025-15084</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15084</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52633</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52633</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-2023-52633</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-311596</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311596</link>
      <description>EUVD-2026-311596</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311596</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52633</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52633</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&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;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52633</guid>
    </item>
    <item>
      <title>GHSA-c7h5-f667-cvc5</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c7h5-f667-cvc5</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&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;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c7h5-f667-cvc5</guid>
    </item>
    <item>
      <title>gsd-2023-52633</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-52633</link>
      <description>gsd-2023-52633</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-52633</guid>
    </item>
    <item>
      <title>OESA-2024-1622 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1622</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):&#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;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe5/0xc30
Read of size 8 at addr ffff8881094223f8 by task stress/7789&#13;
&#13;
CPU: 0 PID: 7789 Comm: stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3
Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
..
 __mutex_lock+0xe5/0xc30
..
 z_erofs_do_read_page+0x8ce/0x1560
..
 z_erofs_readahead+0x31c/0x580
..
Freed by task 7787
 kasan_save_stack+0x1e/0x40
 kasan_set_track+0x20/0x30
 kasan_set_free_info+0x20/0x40
 __kasan_slab_free+0x10c/0x190
 kmem_cache_free+0xed/0x380
 rcu_core+0x3d5/0xc90
 __do_softirq+0x12d/0x389&#13;
&#13;
Last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x97/0xb0
 call_rcu+0x3d/0x3f0
 erofs_shr…&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):&#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;
erofs: fix pcluster use-after-free on UP platforms&#13;
&#13;
During stress testing with CONFIG_SMP disabled, KASAN reports as below:&#13;
&#13;
==================================================================
BUG: KASAN: use-after-free in __mutex_lock+0xe5/0xc30
Read of size 8 at addr ffff8881094223f8 by task stress/7789&#13;
&#13;
CPU: 0 PID: 7789 Comm: stress Not tainted 6.0.0-rc1-00002-g0d53d2e882f9 #3
Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
..
 __mutex_lock+0xe5/0xc30
..
 z_erofs_do_read_page+0x8ce/0x1560
..
 z_erofs_readahead+0x31c/0x580
..
Freed by task 7787
 kasan_save_stack+0x1e/0x40
 kasan_set_track+0x20/0x30
 kasan_set_free_info+0x20/0x40
 __kasan_slab_free+0x10c/0x190
 kmem_cache_free+0xed/0x380
 rcu_core+0x3d5/0xc90
 __do_softirq+0x12d/0x389&#13;
&#13;
Last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x97/0xb0
 call_rcu+0x3d/0x3f0
 erofs_shr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1622</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52633</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52633</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-aws-5.15, Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-hwe-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15 and 36 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: time-travel: fix time corruption In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that&amp;#39;s incompatible with the forward, and we&amp;#39;ll crash because time goes backwards when we do the forwarding. Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-aws-5.15, Ubuntu:20.04:LTS: linux-azure-5.15, Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-gkeop-5.15, Ubuntu:20.04:LTS: linux-hwe-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-intel-iotg-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-nvidia-tegra-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15 and 36 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: time-travel: fix time corruption In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we still get timer interrupts. These can happen at arbitrary points in time, i.e. while in timer_read(), which pushes time forward just a little bit. Then, if we happen to get the interrupt after calculating the new time to push to, but before actually finishing that, the interrupt will set the time to a value that&amp;#39;s incompatible with the forward, and we&amp;#39;ll crash because time goes backwards when we do the forwarding. Fix this by reading the time_travel_time, calculating the adjustment, and doing the adjustment all with interrupts disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52633</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0749 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0749</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service 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 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-0749</guid>
    </item>
  </channel>
</rss>
