CVE-2021-47008KVM: SVM: Make sure GHCB is mapped before updating
- 5.5MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Make sure GHCB is mapped before updating Access to the GHCB is mainly in the VMGEXIT path and it is known that the GHCB will be mapped. But there are two paths where it is possible the GHCB might not be mapped. The sev_vcpu_deliver_sipi_vector() routine will update the GHCB to inform the caller of the AP Reset Hold NAE event that a SIPI has been delivered. However, if a SIPI is performed without a corresponding AP Reset Hold, then the GHCB might not be mapped (depending on the previous VMEXIT), which will result in a NULL pointer dereference. The svm_complete_emulated_msr() routine will update the GHCB to inform the caller of a RDMSR/WRMSR operation about any errors. While it is likely that the GHCB will be mapped in this situation, add a safe guard in this path to be certain a NULL pointer dereference is not encountered.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected f1c6366e304328de301be362eca905a3503ff33b – < fb9e14f4f8217a0980f8da2c8ff70dee058cbe47
- affected f1c6366e304328de301be362eca905a3503ff33b – < fd722a57fe0b80133dacae4e1c852ee4212f9b2e
- affected f1c6366e304328de301be362eca905a3503ff33b – < a3ba26ecfb569f4aa3f867e80c02aa65f20aadad
- affected 5.11
- unaffected < 5.11
- unaffected 5.11.22 – ≤ 5.11.*
- unaffected 5.12.5 – ≤ 5.12.*
- unaffected 5.13 – ≤ *
References
References3
- https://git.kernel.org/stable/c/fb9e14f4f8217a0980f8da2c8ff70dee058cbe47 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/fd722a57fe0b80133dacae4e1c852ee4212f9b2e (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/a3ba26ecfb569f4aa3f867e80c02aa65f20aadad (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2021-33656 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2021-47008)Record last updated .