Bug 1228019 (CVE-2022-48793) - VUL-0: CVE-2022-48793: kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Summary: VUL-0: CVE-2022-48793: kernel: KVM: x86: nSVM: fix potential NULL derefernce ...
Status: NEW
Alias: CVE-2022-48793
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/414233/
Whiteboard: CVSSv3.1:SUSE:CVE-2022-48793:5.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-17 08:46 UTC by SMASH SMASH
Modified: 2024-07-17 09:15 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-07-17 08:46:38 UTC
In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: nSVM: fix potential NULL derefernce on nested migration

Turns out that due to review feedback and/or rebases
I accidentally moved the call to nested_svm_load_cr3 to be too early,
before the NPT is enabled, which is very wrong to do.

KVM can't even access guest memory at that point as nested NPT
is needed for that, and of course it won't initialize the walk_mmu,
which is main issue the patch was addressing.

Fix this for real.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48793
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48793.mbox
https://git.kernel.org/stable/c/74b426bea4f7e3b081add2b88d4fba16d3af7ab6
https://git.kernel.org/stable/c/352193edda48e08e8824a7ece09aec830a603cfe
https://git.kernel.org/stable/c/e1779c2714c3023e4629825762bcbc43a3b943df
https://www.cve.org/CVERecord?id=CVE-2022-48793
https://bugzilla.redhat.com/show_bug.cgi?id=2298129