RISC-V: KVM: Serialize IMSIC attributes with vCPU migration
Summary
| CVE | CVE-2026-98465 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:16:56 UTC |
| Updated | 2026-10-24 14:16:43 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
EPSS: 0.002000000 probability, percentile 0.092880000 (date 2026-10-21)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H |
| 3.1 | CNA | DECLARED | 7 | HIGH | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
ChangedConfidentiality
LowIntegrity
LowAvailability
HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected db8b7e97d6137a28b2bfc07e591d54da268f0c36 6c2bcf6b173d4afed883cceea9d47f2c5194161d git | Not specified |
| CNA | Linux | Linux | affected db8b7e97d6137a28b2bfc07e591d54da268f0c36 a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98 git | Not specified |
| CNA | Linux | Linux | affected db8b7e97d6137a28b2bfc07e591d54da268f0c36 c525772c304c971b0d3a1f2898dedbae653efe90 git | Not specified |
| CNA | Linux | Linux | affected db8b7e97d6137a28b2bfc07e591d54da268f0c36 71acbea44e78665ea90e3c310fca6bbdcc0252db git | Not specified |
| CNA | Linux | Linux | affected db8b7e97d6137a28b2bfc07e591d54da268f0c36 8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc git | Not specified |
| CNA | Linux | Linux | affected 6.5 | Not specified |
| CNA | Linux | Linux | unaffected 6.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.112 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.55 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.9 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/71acbea44e78665ea90e3c310fca6bbdcc0252db | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c525772c304c971b0d3a1f2898dedbae653efe90 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6c2bcf6b173d4afed883cceea9d47f2c5194161d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.