CVE-2021-46978KVM: nVMX: Always make an attempt to map eVMCS after migration
- 7.8HighCVSS 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: nVMX: Always make an attempt to map eVMCS after migration When enlightened VMCS is in use and nested state is migrated with vmx_get_nested_state()/vmx_set_nested_state() KVM can't map evmcs page right away: evmcs gpa is not 'struct kvm_vmx_nested_state_hdr' and we can't read it from VP assist page because userspace may decide to restore HV_X64_MSR_VP_ASSIST_PAGE after restoring nested state (and QEMU, for example, does exactly that). To make sure eVMCS is mapped /vmx_set_nested_state() raises KVM_REQ_GET_NESTED_STATE_PAGES request. Commit f2c7ef3ba955 ("KVM: nSVM: cancel KVM_REQ_GET_NESTED_STATE_PAGES on nested vmexit") added KVM_REQ_GET_NESTED_STATE_PAGES clearing to nested_vmx_vmexit() to make sure MSR permission bitmap is not switched when an immediate exit from L2 to L1 happens right after migration (caused by a pending event, for example). Unfortunately, in the exact same situation we still need to have eVMCS mapped so nested_sync_vmcs12_to_shadow() reflects changes in VMCS12 to eVMCS. As a band-aid, restore nested_get_evmcs_page() when clearing KVM_REQ_GET_NESTED_STATE_PAGES in nested_vmx_vmexit(). The 'fix' is far from being ideal as we can't easily propagate possible failures and even if we could, this is most likely already too late to do so. The whole 'KVM_REQ_GET_NESTED_STATE_PAGES' idea for mapping eVMCS after migration seems to be fragile as we diverge too much from the 'native' path when vmptr loading happens on vmx_set_nested_state().
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 |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 0faceb7d6dda6f370ff1fa0464d7180f7e5cb417 – < c8bf64e3fb77cc19bad146fbe26651985b117194
- affected f2c7ef3ba9556d62a7e2bb23b563c6510007d55c – < 200a45649ab7361bc80c70aebf7165b64f9a6c9f
- affected f2c7ef3ba9556d62a7e2bb23b563c6510007d55c – < bd0e8455b85b651a4c77de9616e307129b15aaa7
- affected f2c7ef3ba9556d62a7e2bb23b563c6510007d55c – < f5c7e8425f18fdb9bdb7d13340651d7876890329
- affected 5.10.13 – < 5.10.38
- affected 5.11
- unaffected < 5.11
- unaffected 5.10.38 – ≤ 5.10.*
- unaffected 5.11.22 – ≤ 5.11.*
- unaffected 5.12.5 – ≤ 5.12.*
- unaffected 5.13 – ≤ *
References
References4
- https://git.kernel.org/stable/c/c8bf64e3fb77cc19bad146fbe26651985b117194 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/200a45649ab7361bc80c70aebf7165b64f9a6c9f (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/bd0e8455b85b651a4c77de9616e307129b15aaa7 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/f5c7e8425f18fdb9bdb7d13340651d7876890329 (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-33626 (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-46978)Record last updated .