CVE-2021-47389
Last modified
CVE-2021-47389 is a medium-severity vulnerability rated 5.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: fix missing sev_decommission in sev_receive_start 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: The RECEIVE_START command is the only command other than the LAUNCH_START command that generates a new guest context and guest handle. 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. Note, LAUNCH_START suffered the same bug, but was previously fixed by commit 934002cd660b ("KVM: SVM: Call SEV Guest Decommission if ASID binding fails").. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: fix missing sev_decommission in sev_receive_start 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: The RECEIVE_START command is the only command other than the LAUNCH_START command that generates a new guest context and guest handle. 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. Note, LAUNCH_START suffered the same bug, but was previously fixed by commit 934002cd660b ("KVM: SVM: Call SEV Guest Decommission if ASID binding fails").
Metrics
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 5.14.10 | — |
| Linux | Linux Kernel | 5.15 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2021-47389?
How severe is CVE-2021-47389?
How do I fix CVE-2021-47389?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-47383In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2021-47384In the Linux kernel, the following vulnerability has been re…5.3
- CVE-2021-47385In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47386In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47387In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47388In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47390In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2021-47391In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47392In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47393In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2021-47394In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47395In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2021-47389?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST