CVE-2026-98464·Kernel vulnerability
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.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.17% — higher than 6% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-98464 scores 9.3 on CVSS, so a successful attack would be serious — but at 0.17%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version to resolve a critical race condition in RISC-V KVM timer handling that can cause use-after-free memory corruption. Users should upgrade to kernel 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9, or newer depending on their current kernel branch, or install your Linux distribution's patched kernel package.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Run 'uname -r' to check your current kernel version and compare against the fixed versions: 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9, or 7.3+
- Verify RISC-V KVM is in use by checking if CONFIG_KVM is enabled: grep CONFIG_KVM /boot/config-$(uname -r)
- Search kernel logs for use-after-free memory errors: dmesg | grep -i 'use-after-free\|KASAN\|slab-use-after-free'
- After patching, reboot and re-run 'uname -r' to confirm the new kernel version is active
FAQ
What is CVE-2026-98464?
This is a critical race condition in the Linux kernel's RISC-V KVM subsystem where timer cleanup and execution callbacks can race, allowing the timer callback to access freed virtual CPU memory during VM teardown. This leads to kernel heap corruption and potential privilege escalation.
Is CVE-2026-98464 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are available. However, the severity is critical and exploitation requires only guest-side timer operations combined with VM shutdown.
What versions of Kernel are affected by CVE-2026-98464?
Multiple kernel branches are affected. The fix is available in: 6.1.189+, 6.6.158+, 6.12.112+, 6.18.55+, 7.2.9+, and mainline 7.3+. Versions prior to these are vulnerable if they contain the non-Sstc hrtimer callback code.
How do I check if my server is vulnerable to CVE-2026-98464?
Run 'uname -r' and compare your kernel version against the patched versions listed above. If you're running a kernel branch with a version number lower than the fixed version for that branch, your system is vulnerable if RISC-V KVM is enabled.
Does Defensia detect CVE-2026-98464?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98464 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/2af03b606aadaaeb386658ef798c79bdcdef87c1
- https://git.kernel.org/stable/c/3cc6184bd5920c9685d87f4e260568feba08650d
- https://git.kernel.org/stable/c/9bdbae64ae0dab93041ebc57ec4e93def793fc2d
- https://git.kernel.org/stable/c/aaad136d56d91252517272b68cd533e5714698d5
- https://git.kernel.org/stable/c/e66aced74f0122380603c9910a71d77618b28f0e
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98464. Free for 1 server.
Get started free