Skip to main content

Linux Kernel CVE-2026-98465

| EUVDEUVD-2026-103705 HIGH
2026-10-18 Linux GHSA-95qg-qjx7-9h4r
7.0
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local privileged KVM/VMM access on RISC-V host
  2. Delivery
    Issue IMSIC GET/SET attribute ioctl
  3. Exploit
    Race concurrent vCPU migration releasing HGEI
  4. Execution
    Operation uses stale CPU/HGEI tuple
  5. Impact
    Access another vCPU's interrupt file

Vulnerability Assessment

Exploitation Conditions

Requires a RISC-V system running the Linux kernel as a KVM host with AIA IMSIC interrupt virtualization in use, plus local attacker ability (PR:L) to issue KVM device ioctls (GET/SET attribute) against an IMSIC VS-file. The flaw is only reachable by winning a timing race: the attribute ioctl must snapshot the physical CPU and HGEI of a VS-file concurrently with a vCPU migration (a KVM_RUN on another thread) that releases and reallocates that HGEI. Limiting factors that reduce realistic risk: RISC-V-only exposure, the need for existing host/VMM-level privileges, no remote reachability (AV:L), and a timing-dependent window reflected in AC:H, making reliable exploitation difficult.

Impact

The input CVSS of 7.0 (High) is driven mainly by the scope change (S:C) and high availability impact (A:H), but the exploitability metrics temper real-world urgency: the vector is local (AV:L), complexity is high (AC:H, consistent with the race window the description explains - a snapshot of the physical CPU/HGEI tuple taken before a concurrent vCPU migration releases it), and low privileges are required (PR:L), meaning the attacker must already have host-side access to issue KVM device ioctls. The threat-intel signals reinforce a measured posture rather than an emergency: EPSS is 0.20% (9th percentile), the CVE is NOT listed in CISA KEV, and no public exploit is identified in the provided data - only kernel.org patch commits and the NVD/EUVD entries. The vendor priority label is 'this_week', which is consistent with a patchable, non-emergency issue. The signals are internally consistent (low EPSS, no KEV, no PoC, local+race-gated exploitation all point the same way); there is no CVSS-vs-description conflict here, since the description confirms both the local ioctl surface and the concurrency trigger implied by AC:H. Net: a legitimate but not top-of-queue priority - real but constrained to RISC-V hosts running KVM with AIA IMSIC virtualization and a privileged local actor able to win a timing race.

Exploit ScenarioDerived

On a RISC-V host running KVM with AIA IMSIC virtualization, a local privileged actor (e.g., a compromised or malicious VMM/management thread) issues a KVM GET/SET attribute ioctl against an IMSIC VS-file while, on another thread, a vCPU migration releases and reallocates the underlying HGEI. By winning this race, the attribute operation uses a stale physical-CPU/HGEI tuple and reads or writes the interrupt file now owned by a different vCPU. No public exploit code is identified in the available data, and the timing-dependent nature (AC:H) makes reliable triggering non-trivial.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 24, 2026

A race condition in the Linux kernel's RISC-V KVM support for AIA IMSIC interrupt virtualization lets a local user who can issue KVM device ioctls read or modify another vCPU's interrupt file. The kvm_riscv_aia_imsic_rw_attr() handler snapshots the physical CPU and HGEI of an IMSIC VS-file without serialization against a concurrent KVM_RUN, so a vCPU migration can release and reallocate that HGEI before the stale tuple is used, giving a GET or SET attribute access to the new owner's VS-file. Exposure is limited to RISC-V KVM hosts using IMSIC, the timing window is narrow (AC:H), and no public exploit or CISA KEV entry exists at time of analysis, with EPSS at 0.20% (9th percentile); vendor fixes are available in 6.12.112, 6.18.55, 7.2.9 and 7.3-rc5.

RemediationAI

Vendor-released patches address the race: update to Linux 6.12.112, 6.18.55, 7.2.9, or 7.3-rc5 (or apply the referenced kernel.org stable commits) on any RISC-V system running KVM with AIA IMSIC interrupt virtualization. The fix is the mutex serialization described in the commit, so the affected distributions should pick up those stable releases rather than relying on configuration changes. Until the kernel is updated, the practical compensating control is to restrict which local accounts may open /dev/kvm and issue KVM device ioctls, since the vector requires low-privileged local access (PR:L) to that interface - the trade-off is that any user or service that legitimately manages VMs loses that capability. No other workaround is documented in the available references.

Affected VersionsENISA

Linux patch: 7.3-rc5
Linux db8b7e97d6137a28b2bfc07e591d54da268f0c36 <a29c5d2dd2ef9a8617a9a6d5585696d5f149cd98
Linux db8b7e97d6137a28b2bfc07e591d54da268f0c36 <8ae12ccaec6ec74945d8c1ef39f2c1b8df779abc
Linux 6.5
Linux patch: 6.18.55
Linux db8b7e97d6137a28b2bfc07e591d54da268f0c36 <c525772c304c971b0d3a1f2898dedbae653efe90
Linux patch: 6.12.112
Linux patch: 7.2.9
Linux db8b7e97d6137a28b2bfc07e591d54da268f0c36 <71acbea44e78665ea90e3c310fca6bbdcc0252db
Linux patch: 0

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw lives in the RISC-V AIA (Advanced Interrupt Architecture) IMSIC emulation inside KVM. An IMSIC VS-file is the per-vCPU guest interrupt file that KVM exposes through device ioctls (GET/SET attribute), handled by kvm_riscv_aia_imsic_rw_attr(). KVM device ioctls are not serialized against KVM_RUN, so the handler can snapshot the physical CPU and HGEI belonging to a VS-file while another thread migrates the vCPU, releasing that HGEI for reallocation. If the interrupt file is recycled to a different vCPU before imsic_vsfile_rw() dereferences the cached tuple, the attribute operation lands on the new owner's interrupt file rather than the intended one, producing cross-vCPU disclosure and tampering. No CWE was supplied; the root cause is missing locking around a state snapshot rather than a memory-safety defect. The upstream fix holds the target vCPU mutex across the whole IMSIC attribute operation, preventing migration and recycling of the VS-file until the access completes, and takes the mutex killably so the device ioctl stays interruptible while waiting for KVM_RUN to finish.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
vuln.today AI 7.0 HIGH

Local KVM ioctl surface (AV:L) with privileged host access (PR:L); the described migration race makes it timing-dependent (AC:H); cross-vCPU interrupt-file access crosses a security boundary (S:C) with limited read/write and potential interrupt-delivery disruption (A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:L/SI:L/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 24, 2026 - 14:22 NVD
7.0 (HIGH)
Patch available
Oct 18, 2026 - 16:02 EUVD
CVE Published
Oct 18, 2026 - 15:15 cve.org
HIGH 7.0
CVE Published
Oct 18, 2026 - 15:15 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

CVE-2026-98465 is a high-severity race condition in Linux kernel's RISC-V KVM support that could allow a local user with KVM device access to compromise interrupt virtualization integrity. Only RISC-V KVM hosts using IMSIC are exposed, and the narrow timing window and lack of public exploitation limit immediate risk. Leadership should prioritize patching these systems to prevent potential privilege escalation or data corruption.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
RISC-V KVM AIA IMSIC virtualization is a niche, rarely deployed kernel subsystem
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy