GHSA-J632-93GC-R86Q
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Don't WARN on an unknown VM ioctl in protected mode
kvm_pkvm_ioctl_allowed() WARNs when kvm_get_cap_for_kvm_ioctl() doesn't find the ioctl number in vm_ioctl_caps[], and kvm_arch_vm_ioctl() calls it for every number the generic code doesn't handle, so ioctl(vm_fd, 0xdeadbeef) from userspace taints a pKVM host and panics it under panic_on_warn. The lookup is fed userspace input: return false, and userspace gets the -EINVAL kvm_arch_vm_ioctl() returns for that number on a host without pKVM.
{
"affected": [],
"aliases": [
"CVE-2026-98470"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:16:57Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Don\u0027t WARN on an unknown VM ioctl in protected mode\n\nkvm_pkvm_ioctl_allowed() WARNs when kvm_get_cap_for_kvm_ioctl() doesn\u0027t\nfind the ioctl number in vm_ioctl_caps[], and kvm_arch_vm_ioctl() calls\nit for every number the generic code doesn\u0027t handle, so\nioctl(vm_fd, 0xdeadbeef) from userspace taints a pKVM host and panics it\nunder panic_on_warn. The lookup is fed userspace input: return false,\nand userspace gets the -EINVAL kvm_arch_vm_ioctl() returns for that\nnumber on a host without pKVM.",
"id": "GHSA-j632-93gc-r86q",
"modified": "2026-10-18T18:31:50Z",
"published": "2026-10-18T18:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98470"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/49d9d295d69d07e850cae35933ba8519e2915f26"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cc53eb5c6515e3221314624a22c9da9c80a67f63"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.