<?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>Mon, 16 Nov 2026 20:41:17 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-351551</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-351551</link>
      <description>EUVD-2026-351551</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-351551</guid>
    </item>
    <item>
      <title>fkie_cve-2026-20763</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-20763</link>
      <description>&lt;p&gt;Incorrect calculation for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect calculation for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-20763</guid>
    </item>
    <item>
      <title>GHSA-wgvc-hf5h-m5h7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wgvc-hf5h-m5h7</link>
      <description>&lt;p&gt;Incorrect calculation for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect calculation for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wgvc-hf5h-m5h7</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0485 — `enter_l2_vcpu` passes the wrong RCX operand to `TDG.VP.ENTER`</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0485</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tdx-guest&lt;/p&gt;
&lt;p&gt;`tdx_guest::tdcall::enter_l2_vcpu()` invokes the `TDG.VP.ENTER` TDCALL. RCX
must carry the L2 VM index in bits 53:52 and the invalidation control value
(`InvdTranslations`, 0 to 3) in bits 1:0. The function computed that value as
`(l2_vm_idx &amp;lt;&amp;lt; 52) | (invd_translations as u64)`, but then passed the raw
`l2_vm_idx` in RCX instead.&lt;/p&gt;
&lt;p&gt;As a result, the TDX module received an operand that differs from the
caller&amp;#39;s request. The VM index field was 0, and the low bits of the index
were interpreted as the invalidation control value. For example, VM 1 with
`InvdTlb` (2) should produce `0x0010_0000_0000_0002`, but produced `0x1`.&lt;/p&gt;
&lt;p&gt;Intel describes the issue as an incorrect calculation and classifies it as
escalation of privilege, with a CVSS 4.0 base score of 4.6, in
INTEL-SA-01462.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commit
[`311d33b`](https://github.com/intel/confidential-computing.tdx.tdx-guest/commit/311d33b18a5bef5dc67c9b0c86587dd00c77027e),
released in 0.3.1, which passes the computed RCX value.&lt;/p&gt;
&lt;p&gt;Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tdx-guest&lt;/p&gt;
&lt;p&gt;`tdx_guest::tdcall::enter_l2_vcpu()` invokes the `TDG.VP.ENTER` TDCALL. RCX
must carry the L2 VM index in bits 53:52 and the invalidation control value
(`InvdTranslations`, 0 to 3) in bits 1:0. The function computed that value as
`(l2_vm_idx &amp;lt;&amp;lt; 52) | (invd_translations as u64)`, but then passed the raw
`l2_vm_idx` in RCX instead.&lt;/p&gt;
&lt;p&gt;As a result, the TDX module received an operand that differs from the
caller&amp;#39;s request. The VM index field was 0, and the low bits of the index
were interpreted as the invalidation control value. For example, VM 1 with
`InvdTlb` (2) should produce `0x0010_0000_0000_0002`, but produced `0x1`.&lt;/p&gt;
&lt;p&gt;Intel describes the issue as an incorrect calculation and classifies it as
escalation of privilege, with a CVSS 4.0 base score of 4.6, in
INTEL-SA-01462.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commit
[`311d33b`](https://github.com/intel/confidential-computing.tdx.tdx-guest/commit/311d33b18a5bef5dc67c9b0c86587dd00c77027e),
released in 0.3.1, which passes the computed RCX value.&lt;/p&gt;
&lt;p&gt;Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0485</guid>
    </item>
  </channel>
</rss>
