KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.27, 7.0.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Avoid clearing VMCB_LBR in vmcb12 svm_copy_lbrs() always marks VMCB_LBR dirty in the destination VMCB. However, nested_svm_vmexit() uses it to copy LBRs to vmcb12, and clearing clean bits in vmcb12 is not architecturally defined. Move vmcb_mark_dirty() to callers and drop it for vmcb12. This also facilitates incoming refactoring that does not pass the entire VMCB to svm_copy_lbrs().
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · fixed in 165b08d2d1346dce5ed43db65e10f3194b9ae2fe; From d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · fixed in 11d347b7edf5093d69aca72317300798a32bfd6b; From d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · fixed in a3f0981a5a0e0bd51ad74cc7d9eed32294b24002; From d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · fixed in 9efe23568806d1cd06f7d146f9b3037b8d585a9f; From d20c796ca3709801f8a7fa36e8770a3dd8ebd34e · fixed in b53ab5167a81537777ac780bbd93d32613aa3bda
- Linux Linux
5.19
- KernelLinux
From 5.19.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.27; From 6.19.0 · fixed in 7.0.4