RISC-V: KVM: Serialize IMSIC attributes with vCPU migration
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.12.112, 6.18.55, 6.6.160, 7.2.9
- CVEs
- CVE-2026-98465
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 19:39 UTC · Revision 1
Source evidence
RISC-V: KVM: Serialize IMSIC attributes with vCPU migration
core-osv · Original sourcePublished 18 Oct 2026, 15:15 UTC
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.
osv:CVE-2026-98465
Kernel
Fixed versions: 6.6.160, 6.12.112, 6.18.55, 7.2.9
Complete source record
{
"id": "9c3874d14bb90d95b7d76ed29514a5aa17407defad7ce38b3bc3adbcf7b5494e",
"url": "https://osv.dev/vulnerability/CVE-2026-98465",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RISC-V: KVM: Serialize IMSIC attributes with vCPU migration",
"summary": "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.",
"evidence": "osv:CVE-2026-98465",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.160",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.55",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-98465",
"aliases": [
"CVE-2026-98465"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "db8b7e97d6137a28b2bfc07e591d54da268f0c36"
},
{
"fixed": "6c2bcf6b173d4afed883cceea9d47f2c5194161d"
},
{
"fixed": "a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98"
},
{
"fixed": "c525772c304c971b0d3a1f2898dedbae653efe90"
},
{
"fixed": "71acbea44e78665ea90e3c310fca6bbdcc0252db"
},
{
"fixed": "8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98465.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.5.0"
},
{
"fixed": "6.6.160"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.55"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98465.json"
}
}
],
"modified": "2026-10-28T02:30:38.629561024Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/6c2bcf6b173d4afed883cceea9d47f2c5194161d",
"https://git.kernel.org/stable/c/71acbea44e78665ea90e3c310fca6bbdcc0252db",
"https://git.kernel.org/stable/c/8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc",
"https://git.kernel.org/stable/c/a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98",
"https://git.kernel.org/stable/c/c525772c304c971b0d3a1f2898dedbae653efe90",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98465.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98465",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98465.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98465",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 506267,
"published_at": "2026-10-18T15:15:17.498+00:00"
}