<?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>Tue, 06 Oct 2026 14:06:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47389 — KVM: SVM: fix missing sev_decommission in sev_receive_start</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47389</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: fix missing sev_decommission in sev_receive_start&lt;/p&gt;
&lt;p&gt;DECOMMISSION the current SEV context if binding an ASID fails after
RECEIVE_START.  Per AMD&amp;#39;s SEV API, RECEIVE_START generates a new guest
context and thus needs to be paired with DECOMMISSION:&lt;/p&gt;
&lt;p&gt;The RECEIVE_START command is the only command other than the LAUNCH_START
     command that generates a new guest context and guest handle.&lt;/p&gt;
&lt;p&gt;The missing DECOMMISSION can result in subsequent SEV launch failures,
as the firmware leaks memory and might not able to allocate more SEV
guest contexts in the future.&lt;/p&gt;
&lt;p&gt;Note, LAUNCH_START suffered the same bug, but was previously fixed by
commit 934002cd660b (&amp;#34;KVM: SVM: Call SEV Guest Decommission if ASID
binding fails&amp;#34;).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;KVM: SVM: fix missing sev_decommission in sev_receive_start&lt;/p&gt;
&lt;p&gt;DECOMMISSION the current SEV context if binding an ASID fails after
RECEIVE_START.  Per AMD&amp;#39;s SEV API, RECEIVE_START generates a new guest
context and thus needs to be paired with DECOMMISSION:&lt;/p&gt;
&lt;p&gt;The RECEIVE_START command is the only command other than the LAUNCH_START
     command that generates a new guest context and guest handle.&lt;/p&gt;
&lt;p&gt;The missing DECOMMISSION can result in subsequent SEV launch failures,
as the firmware leaks memory and might not able to allocate more SEV
guest contexts in the future.&lt;/p&gt;
&lt;p&gt;Note, LAUNCH_START suffered the same bug, but was previously fixed by
commit 934002cd660b (&amp;#34;KVM: SVM: Call SEV Guest Decommission if ASID
binding fails&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47389</guid>
    </item>
  </channel>
</rss>
