<?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 20:30:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-10270</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-10270</link>
      <description>bdu:2024-10270</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-10270</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52874</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52874</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2023-52874</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0632 — 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-0632</link>
      <description>certfr-2024-avi-0632</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632</guid>
    </item>
    <item>
      <title>EUVD-2026-345086</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345086</link>
      <description>EUVD-2026-345086</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345086</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52874</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52874</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro&lt;/p&gt;
&lt;p&gt;In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the
untrusted VMM, the registers that the TDX guest shares to the VMM need
to be cleared to avoid speculative execution of VMM-provided values.&lt;/p&gt;
&lt;p&gt;RSI is specified in the bitmap of those registers, but it is missing
when zeroing out those registers in the current TDX_HYPERCALL.&lt;/p&gt;
&lt;p&gt;It was there when it was originally added in commit 752d13305c78
(&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was
later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt
frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is
later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be
(&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34;
but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back.&lt;/p&gt;
&lt;p&gt;Fix by adding it back.&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/tdx: Zero out the missing RSI in TDX_HYPERCALL macro&lt;/p&gt;
&lt;p&gt;In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the
untrusted VMM, the registers that the TDX guest shares to the VMM need
to be cleared to avoid speculative execution of VMM-provided values.&lt;/p&gt;
&lt;p&gt;RSI is specified in the bitmap of those registers, but it is missing
when zeroing out those registers in the current TDX_HYPERCALL.&lt;/p&gt;
&lt;p&gt;It was there when it was originally added in commit 752d13305c78
(&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was
later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt
frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is
later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be
(&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34;
but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back.&lt;/p&gt;
&lt;p&gt;Fix by adding it back.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52874</guid>
    </item>
    <item>
      <title>GHSA-5h67-9rvr-r9x6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5h67-9rvr-r9x6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro&lt;/p&gt;
&lt;p&gt;In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the
untrusted VMM, the registers that the TDX guest shares to the VMM need
to be cleared to avoid speculative execution of VMM-provided values.&lt;/p&gt;
&lt;p&gt;RSI is specified in the bitmap of those registers, but it is missing
when zeroing out those registers in the current TDX_HYPERCALL.&lt;/p&gt;
&lt;p&gt;It was there when it was originally added in commit 752d13305c78
(&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was
later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt
frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is
later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be
(&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34;
but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back.&lt;/p&gt;
&lt;p&gt;Fix by adding it back.&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/tdx: Zero out the missing RSI in TDX_HYPERCALL macro&lt;/p&gt;
&lt;p&gt;In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the
untrusted VMM, the registers that the TDX guest shares to the VMM need
to be cleared to avoid speculative execution of VMM-provided values.&lt;/p&gt;
&lt;p&gt;RSI is specified in the bitmap of those registers, but it is missing
when zeroing out those registers in the current TDX_HYPERCALL.&lt;/p&gt;
&lt;p&gt;It was there when it was originally added in commit 752d13305c78
(&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was
later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt
frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is
later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be
(&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34;
but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back.&lt;/p&gt;
&lt;p&gt;Fix by adding it back.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5h67-9rvr-r9x6</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2571-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2571-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:2571-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52874</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52874</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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the untrusted VMM, the registers that the TDX guest shares to the VMM need to be cleared to avoid speculative execution of VMM-provided values. RSI is specified in the bitmap of those registers, but it is missing when zeroing out those registers in the current TDX_HYPERCALL. It was there when it was originally added in commit 752d13305c78 (&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be (&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34; but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back. Fix by adding it back.&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 67 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the untrusted VMM, the registers that the TDX guest shares to the VMM need to be cleared to avoid speculative execution of VMM-provided values. RSI is specified in the bitmap of those registers, but it is missing when zeroing out those registers in the current TDX_HYPERCALL. It was there when it was originally added in commit 752d13305c78 (&amp;#34;x86/tdx: Expand __tdx_hypercall() to handle more arguments&amp;#34;), but was later removed in commit 1e70c680375a (&amp;#34;x86/tdx: Do not corrupt frame-pointer in __tdx_hypercall()&amp;#34;), which was correct because %rsi is later restored in the &amp;#34;pop %rsi&amp;#34;.  However a later commit 7a3a401874be (&amp;#34;x86/tdx: Drop flags from __tdx_hypercall()&amp;#34;) removed that &amp;#34;pop %rsi&amp;#34; but forgot to add the &amp;#34;xor %rsi, %rsi&amp;#34; back. Fix by adding it back.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52874</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1197 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe 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-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</guid>
    </item>
  </channel>
</rss>
