<?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 21:38:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07873</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07873</link>
      <description>bdu:2025-07873</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07873</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53114</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53114</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-53114</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1102 — 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-1102</link>
      <description>certfr-2024-avi-1102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-1102</guid>
    </item>
    <item>
      <title>EUVD-2026-313616</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313616</link>
      <description>EUVD-2026-313616</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313616</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53114</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53114</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client&lt;/p&gt;
&lt;p&gt;A number of Zen4 client SoCs advertise the ability to use virtualized
VMLOAD/VMSAVE, but using these instructions is reported to be a cause
of a random host reboot.&lt;/p&gt;
&lt;p&gt;These instructions aren&amp;#39;t intended to be advertised on Zen4 client
so clear the capability.&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;x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client&lt;/p&gt;
&lt;p&gt;A number of Zen4 client SoCs advertise the ability to use virtualized
VMLOAD/VMSAVE, but using these instructions is reported to be a cause
of a random host reboot.&lt;/p&gt;
&lt;p&gt;These instructions aren&amp;#39;t intended to be advertised on Zen4 client
so clear the capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53114</guid>
    </item>
    <item>
      <title>GHSA-rgw8-cw3p-qv66</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rgw8-cw3p-qv66</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client&lt;/p&gt;
&lt;p&gt;A number of Zen4 client SoCs advertise the ability to use virtualized
VMLOAD/VMSAVE, but using these instructions is reported to be a cause
of a random host reboot.&lt;/p&gt;
&lt;p&gt;These instructions aren&amp;#39;t intended to be advertised on Zen4 client
so clear the capability.&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;x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client&lt;/p&gt;
&lt;p&gt;A number of Zen4 client SoCs advertise the ability to use virtualized
VMLOAD/VMSAVE, but using these instructions is reported to be a cause
of a random host reboot.&lt;/p&gt;
&lt;p&gt;These instructions aren&amp;#39;t intended to be advertised on Zen4 client
so clear the capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rgw8-cw3p-qv66</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-53114 — x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-53114</link>
      <description>msrc_CVE-2024-53114</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-53114</guid>
    </item>
    <item>
      <title>OESA-2024-2569 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2569</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;
dmaengine: idxd: Let probe fail when workqueue cannot be enabled&#13;
&#13;
The workqueue is enabled when the appropriate driver is loaded and
disabled when the driver is removed. When the driver is removed it
assumes that the workqueue was enabled successfully and proceeds to
free allocations made during workqueue enabling.&#13;
&#13;
Failure during workqueue enabling does not prevent the driver from
being loaded. This is because the error path within drv_enable_wq()
returns success unless a second failure is encountered
during the error path. By returning success it is possible to load
the driver even if the workqueue cannot be enabled and
allocations that do not exist are attempted to be freed during
driver remove.&#13;
&#13;
Some examples of problematic flows:
(a)&#13;
&#13;
 idxd_dmaengine_drv_probe() -&amp;amp;gt; drv_enable_wq() -&amp;amp;gt; idxd_wq_request_irq():
 In above flow, if idxd_wq_request_irq() fails then
 idxd_wq_unmap_portal() is called on error exit path, but
 drv_enable_wq() returns 0 because idxd_wq_disable() succeeds. The
 driver is thus loaded successfully.&#13;
&#13;
 idxd_dmaengine_drv_remove()-&amp;amp;gt;drv_disable_wq()-&amp;amp;gt;idxd_wq_unmap_portal()
 Above flow on driver unload triggers the WARN in devm_iounmap() because
 the device resource has already been removed during error path of
 drv_enable_wq().&#13;
&#13;
(b)&#13;
&#13;
 idxd_dmaengine_drv_probe() -&amp;amp;gt; drv_enable_wq() -&amp;amp;g…&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;
dmaengine: idxd: Let probe fail when workqueue cannot be enabled&#13;
&#13;
The workqueue is enabled when the appropriate driver is loaded and
disabled when the driver is removed. When the driver is removed it
assumes that the workqueue was enabled successfully and proceeds to
free allocations made during workqueue enabling.&#13;
&#13;
Failure during workqueue enabling does not prevent the driver from
being loaded. This is because the error path within drv_enable_wq()
returns success unless a second failure is encountered
during the error path. By returning success it is possible to load
the driver even if the workqueue cannot be enabled and
allocations that do not exist are attempted to be freed during
driver remove.&#13;
&#13;
Some examples of problematic flows:
(a)&#13;
&#13;
 idxd_dmaengine_drv_probe() -&amp;amp;gt; drv_enable_wq() -&amp;amp;gt; idxd_wq_request_irq():
 In above flow, if idxd_wq_request_irq() fails then
 idxd_wq_unmap_portal() is called on error exit path, but
 drv_enable_wq() returns 0 because idxd_wq_disable() succeeds. The
 driver is thus loaded successfully.&#13;
&#13;
 idxd_dmaengine_drv_remove()-&amp;amp;gt;drv_disable_wq()-&amp;amp;gt;idxd_wq_unmap_portal()
 Above flow on driver unload triggers the WARN in devm_iounmap() because
 the device resource has already been removed during error path of
 drv_enable_wq().&#13;
&#13;
(b)&#13;
&#13;
 idxd_dmaengine_drv_probe() -&amp;amp;gt; drv_enable_wq() -&amp;amp;g…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2569</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:4314-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:4314-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:4314-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53114</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53114</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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client A number of Zen4 client SoCs advertise the ability to use virtualized VMLOAD/VMSAVE, but using these instructions is reported to be a cause of a random host reboot. These instructions aren&amp;#39;t intended to be advertised on Zen4 client so clear the capability.&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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Clear virtualized VMLOAD/VMSAVE on Zen4 client A number of Zen4 client SoCs advertise the ability to use virtualized VMLOAD/VMSAVE, but using these instructions is reported to be a cause of a random host reboot. These instructions aren&amp;#39;t intended to be advertised on Zen4 client so clear the capability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53114</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3575 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3575</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-3575</guid>
    </item>
  </channel>
</rss>
