CVE-2021-47407

What it actually does

Failure to check return value of init_srcu_struct() during KVM x86 page track initialization leads to NULL pointer dereference on out-of-memory conditions.

Why it matters to the business

Potential kernel crashes or denial of service affecting virtual machine hosting and hypervisor stability in Linux environments.

How an attack unfolds

An attacker triggers virtual machine initialization under memory pressure to cause the unchecked SRCU failure path, resulting in a NULL dereference during page tracking setup.

How to fix it

Apply the upstream fix that moves the SRCU initialization call earlier in kvm_arch_init_vm and checks its return value; update to a patched Linux kernel version containing this change.

How to confirm the fix worked

Inspect kernel source for the presence of the return-value check on init_srcu_struct() in page tracking initialization and verify the call ordering in kvm_arch_init_vm.

Typical attack path

1. Initiate KVM virtual machine creation
2. Induce out-of-memory condition during arch VM init
3. Trigger page track initialization without valid SRCU struct
4. Cause NULL pointer dereference and kernel fault

How to detect it

Review kernel panic and oops logs for KVM page track or SRCU initialization failures; search dmesg and syslog for NULL pointer dereference traces involving kvm_arch_init_vm.

What your security team should do

• Prioritize kernel updates for all hypervisor hosts running affected KVM code
• Monitor kernel logs for unexpected NULL dereference oops in KVM paths
• Limit untrusted local access that could influence VM initialization timing