VulnerabilityPublished 18 Oct 2026

CVE-2026-98470: Linux kernel · KVM: arm64: Don't WARN on an unknown VM ioctl in protected mode

Source GCVE Database

Authoritative record:CVE-2026-98470· Medium

Not known to be exploited : upgrade to cc53eb5c6515e3221314624a22c9da9c80a67f63 or 49d9d295d69d07e850cae35933ba8519e2915f26 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in cc53eb5c6515e3221314624a22c9da9c80a67f63, 49d9d295d69d07e850cae35933ba8519e2915f26

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-j632-93gc-r86q

What to do

Upgrade Linux kernel to cc53eb5c6515e3221314624a22c9da9c80a67f63 or 49d9d295d69d07e850cae35933ba8519e2915f26.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b12b3b04f6ba072ca5a618a75e546c996be94bd1, < cc53eb5c6515e3221314624a22c9da9c80a67f63	Fixed in cc53eb5c6515e3221314624a22c9da9c80a67f63
LinuxLinux	Affected ≥ b12b3b04f6ba072ca5a618a75e546c996be94bd1, < 49d9d295d69d07e850cae35933ba8519e2915f26	Fixed in 49d9d295d69d07e850cae35933ba8519e2915f26
LinuxLinux	Affected =7.0	Fixed in–

AI-suggested

A fix has been applied to the Linux kernel to resolve this issue. Users should update to the patched kernel version once available. No additional mitigation is required beyond applying the official fix.

Description

A vulnerability in the Linux kernel's KVM arm64 implementation caused a WARN on unknown VM ioctl calls in protected mode, which could lead to a panic on hosts configured with panic_on_warn. This issue occurs because the function kvm_pkvm_ioctl_allowed() triggers a WARN when an ioctl number is not found in vm_ioctl_caps[], and the architecture-specific ioctl handler calls this for unrecognized ioctl numbers. Userspace can trigger this by issuing an ioctl with an arbitrary number, causing the host to become tainted and potentially panic.

References

Community reviews

Loading reviews…