RISC-V: KVM: Synchronize hrtimer callback during teardown
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 · < aaad136d56d91252517272b68cd533e5714698d5| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
RISC-V: KVM: Synchronize hrtimer callback during teardown
The non-Sstc hrtimer callback clears next_set before its final uses of the enclosing vCPU. If teardown observes next_set as false while the callback is still running, kvm_riscv_vcpu_timer_cancel() skips hrtimer_cancel() and kvm_destroy_vcpus() can free the vCPU before the callback enters kvm_riscv_vcpu_set_interrupt().
A guest can arm the timer with SBI TIME and request shutdown with SBI legacy shutdown or SRST. A VMM that honors KVM_EXIT_SYSTEM_EVENT and destroys the VM supplies the teardown side of the race; no post-launch host ioctl is needed to arm or request teardown.
On upstream master 62cc90241548, generic KASAN reported:
BUG: KASAN: slab-use-after-free in do_raw_spin_lock Write of size 4 at addr ff60000005e58898
kvm_riscv_vcpu_set_interrupt kvm_riscv_vcpu_hrtimer_expired __hrtimer_run_queues hrtimer_interrupt
The object was allocated by KVM_CREATE_VCPU and freed concurrently by:
From the CVE record · Linux
In Linux RISC-V KVM without Sstc, a timer callback can continue after vCPU teardown starts, causing a use-after-free. A guest can trigger the race by arming a timer and requesting shutdown if the VMM honors the resulting system event by destroying the VM; no post-launch host ioctl is needed.
Operators of Linux hosts running RISC-V KVM without Sstc should check their kernel versions against the vendor advisory; affected versions were not specified.