<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T15:49:48.647074+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2021-47389</id>
    <title>CVE-2021-47389 — KVM: SVM: fix missing sev_decommission in sev_receive_start</title>
    <updated>2026-10-06T15:49:48.664126+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, linux_kernel</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>KVM: SVM: fix missing sev_decommission in sev_receive_start</p>
<p>DECOMMISSION the current SEV context if binding an ASID fails after
RECEIVE_START.  Per AMD's SEV API, RECEIVE_START generates a new guest
context and thus needs to be paired with DECOMMISSION:</p>
<p>The RECEIVE_START command is the only command other than the LAUNCH_START
     command that generates a new guest context and guest handle.</p>
<p>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.</p>
<p>Note, LAUNCH_START suffered the same bug, but was previously fixed by
commit 934002cd660b ("KVM: SVM: Call SEV Guest Decommission if ASID
binding fails").</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-47389"/>
  </entry>
</feed>
