CVE-2026-98464

RISC-V: KVM: Synchronize hrtimer callback during teardown

  • Critical 9.3

Description

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: kvm_destroy_vcpus kvm_arch_destroy_vm kvm_destroy_vm __fput For deterministic validation, I added mdelay(1000) immediately after the existing next_set = false assignment. This only widens the existing post-clear callback window. A no-delay trace build naturally reached the callback-after-teardown-start/before-deinit ordering in 12 of 200 runs, but 1,500 stock-kernel stress iterations did not produce a KASAN report, so natural reproduction is timing-sensitive. Always invoke hrtimer_cancel() for an initialized timer. Preserve the existing -EINVAL result when the timer is no longer set, but only after synchronizing with a running callback. With this patch, hrtimer_cancel() blocked for the full widened callback window before vCPU destruction. KASAN reported no error in 100 fixed-and-widened runs or 200 fix-only timing-sweep runs.

Key facts

Published
18 Oct 2026
Last changed
24 Oct 2026
Assigned by
Linux
EPSS
0.143% likely to be exploited in the next 30 days, higher than 3.664% of CVEs (scores for 18 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.3CVSS 3.1, Criticalfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding 9bdbae64ae0dab93041ebc57ec4e93def793fc2d (affected)
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding 2af03b606aadaaeb386658ef798c79bdcdef87c1 (affected)
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding e66aced74f0122380603c9910a71d77618b28f0e (affected)
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding ea91f05a55b807ead3166546a2c75f4185ca645f (affected)
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding 3cc6184bd5920c9685d87f4e260568feba08650d (affected)
  • 3a9f66cb25e18a3eeca36c08d9f823a35b3ddc22 up to but excluding aaad136d56d91252517272b68cd533e5714698d5 (affected)
LinuxLinux
  • Default status: affected
  • 5.16 (affected)
  • 0 up to but excluding 5.16 (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References