CVE-2022-48793
published 2024-07-16CVE-2022-48793: 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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.0th percentile
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.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.11-1 (bookworm) | linux 5.16.11-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 232f75d3b4b5456de6f0b671aa86345d62de1473 < 74b426bea4f7e3b081add2b88d4fba16d3af7ab6 | 74b426bea4f7e3b081add2b88d4fba16d3af7ab6 |
| linux | linux | >= 232f75d3b4b5456de6f0b671aa86345d62de1473 < 352193edda48e08e8824a7ece09aec830a603cfe | 352193edda48e08e8824a7ece09aec830a603cfe |
| linux | linux | >= 232f75d3b4b5456de6f0b671aa86345d62de1473 < e1779c2714c3023e4629825762bcbc43a3b943df | e1779c2714c3023e4629825762bcbc43a3b943df |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 5.13 < 5.15.25 | 5.15.25 |
| linux | linux_kernel | >= 5.16 < 5.16.11 | 5.16.11 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration
vendor_redhat·2024-07-16·CVSS 5.5
CVE-2022-48793 [MEDIUM] CWE-476 kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration
kernel: KVM: x86: nSVM: fix potential NULL derefernce on nested migration
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.
A vulnerability was found in the nested.c file in the Linux kernel's KVM driver, where a potential NULL dereference can occur. This happens when the call to load the nested state is executed before Nested Page Tables
Debian
CVE-2022-48793: linux - In the Linux kernel, the following vulnerability has been resolved: KVM: x86: n...
vendor_debian·2022·CVSS 5.5
CVE-2022-48793 [MEDIUM] CVE-2022-48793: linux - In the Linux kernel, the following vulnerability has been resolved: KVM: x86: n...
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.
Scope: local
bookworm: resolved (fixed in 5.16.11-1)
bullseye: resolved
forky: resolved (fixed in 5.16.11-1)
sid: resolved (fixed in 5.16.11-1)
trixie: resolved (fixed in 5.16.11-1)
VulDB
Linux Kernel up to 5.15.24/5.16.10 nSVM nested_svm_load_cr3 initialization (74b426bea4f7/352193edda48/e1779c2714c3 / Nessus ID 239850)
vuldb·2026-07-11·CVSS 5.5
CVE-2022-48793 [MEDIUM] Linux Kernel up to 5.15.24/5.16.10 nSVM nested_svm_load_cr3 initialization (74b426bea4f7/352193edda48/e1779c2714c3 / Nessus ID 239850)
A vulnerability identified as critical has been detected in Linux Kernel up to 5.15.24/5.16.10. This affects the function nested_svm_load_cr3 of the component nSVM. Performing a manipulation results in improper initialization.
This vulnerability is identified as CVE-2022-48793. The attack can only be performed from the local network. There is not any exploit available.
You should upgrade the affected component.
OSV
CVE-2022-48793: In the Linux kernel, the following vulnerability has been resolved: KVM: x86: nSVM: fix potential NULL derefernce on nested migration Turns out that d
osv·2024-07-16·CVSS 5.5
CVE-2022-48793 [MEDIUM] CVE-2022-48793: In the Linux kernel, the following vulnerability has been resolved: KVM: x86: nSVM: fix potential NULL derefernce on nested migration Turns out that d
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.
GHSA
GHSA-p5hp-9793-2w9c: In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Turns out that
ghsa_unreviewed·2024-07-16
CVE-2022-48793 [MEDIUM] CWE-476 GHSA-p5hp-9793-2w9c: In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: nSVM: fix potential NULL derefernce on nested migration
Turns out that
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/352193edda48e08e8824a7ece09aec830a603cfehttps://git.kernel.org/stable/c/74b426bea4f7e3b081add2b88d4fba16d3af7ab6https://git.kernel.org/stable/c/e1779c2714c3023e4629825762bcbc43a3b943dfhttps://git.kernel.org/stable/c/352193edda48e08e8824a7ece09aec830a603cfehttps://git.kernel.org/stable/c/74b426bea4f7e3b081add2b88d4fba16d3af7ab6https://git.kernel.org/stable/c/e1779c2714c3023e4629825762bcbc43a3b943df
2024-07-16
Published