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

> A race condition in Linux KVM allows a privileged attacker to access another vCPU's interrupt file during migration, leading to data exposure or modification.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** AZL-108906, BELL-CVE-2026-98465, DEBIAN-CVE-2026-98465, GHSA-95qg-qjx7-9h4r, UBUNTU-CVE-2026-98465

## What is CVE-2026-98465?

CVE-2026-98465 is a high-severity vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98465?


## How do I fix CVE-2026-98465?

Apply the vendor's patch.

## Is CVE-2026-98465 being exploited?

There is no known exploitation of CVE-2026-98465 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98465 and fix it if it is affected.

What it is: CVE-2026-98465 is a high-severity vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98465 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98465/ (Markdown: https://insights.sbomify.com/CVE-2026-98465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98465
- OSV: https://osv.dev/vulnerability/CVE-2026-98465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98465/
Summaries are generated and may contain mistakes; the official description above is the record.