CVE-2026-43315

Source
https://cve.org/CVERecord?id=CVE-2026-43315
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-43315.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2026-43315
Downstream
Published
2026-05-08T13:11:31.784Z
Modified
2026-06-18T03:56:38.133109987Z
Summary
KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding
Details

In the Linux kernel, the following vulnerability has been resolved:

KVM: nSVM: Remove a user-triggerable WARN on nestedsvmload_cr3() succeeding

Drop the WARN in svmsetnestedstate() on nestedsvmloadcr3() failing as it is trivially easy to trigger from userspace by modifying CPUID after loading CR3. E.g. modifying the state restoration selftest like so:

--- tools/testing/selftests/kvm/x86/statetest.c +++ tools/testing/selftests/kvm/x86/statetest.c @@ -280,7 +280,16 @@ int main(int argc, char *argv[])

             /* Restore state in a new VM.  */
              vcpu = vm_recreate_with_one_vcpu(vm);

- vcpuloadstate(vcpu, state); + + if (stage == 4) { + state->sregs.cr3 = BIT(44); + vcpuloadstate(vcpu, state); + + vcpusetcpuidproperty(vcpu, X86PROPERTYMAXPHY_ADDR, 36); + _vcpunestedstateset(vcpu, &state->nested); + } else { + vcpuloadstate(vcpu, state); + }

              /*
               * Restore XSAVE state in a dummy vCPU, first without doing

generates:

WARNING: CPU: 30 PID: 938 at arch/x86/kvm/svm/nested.c:1877 svmsetnestedstate+0x34a/0x360 [kvmamd] Modules linked in: kvmamd kvm irqbypass [last unloaded: kvm] CPU: 30 UID: 1000 PID: 938 Comm: statetest Tainted: G W 6.18.0-rc7-58e10b63777d-next-vm Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:svmsetnestedstate+0x34a/0x360 [kvmamd] Call Trace: <TASK> kvmarchvcpuioctl+0xf33/0x1700 [kvm] kvmvcpu_ioctl+0x4e6/0x8f0 [kvm] __x64sysioctl+0x8f/0xd0 dosyscall64+0x61/0xad0 entrySYSCALL64afterhwframe+0x4b/0x53

Simply delete the WARN instead of trying to prevent userspace from shoving "illegal" state into CR3. For better or worse, KVM's ABI allows userspace to set CPUID after SREGS, and vice versa, and KVM is very permissive when it comes to guest CPUID. I.e. attempting to enforce the virtual CPU model when setting CPUID could break userspace. Given that the WARN doesn't provide any meaningful protection for KVM or benefit for userspace, simply drop it even though the odds of breaking userspace are minuscule.

Opportunistically delete a spurious newline.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43315.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
b222b0b88162bdef4eceb12a79d5edbbdb23dbfd
Fixed
155ec243ef726f4bc49536fa0bfb565dc011ab17
Fixed
580ea57840864d40e019bc13fd26afdc8d510a2f
Fixed
deb8f6dfd31d94b18dbeeaa8c01fbec5fc70fd2b
Fixed
ce904c8a5bbe697eae0f7e34b07095bd7a6dee19
Fixed
969e5e13ff5c18603f21d1f9f64ec9194e141ac0
Fixed
ebb2ab4f1c87d6b52776292cf7dc16aea48e95f8
Fixed
fc3ba56385d03501eb582e4b86691ba378e556f9

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-43315.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.14.0
Fixed
5.15.202
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.165
Type
ECOSYSTEM
Events
Introduced
6.2.0
Fixed
6.6.128
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.75
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.16
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
6.19.6

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-43315.json"