OESA-2026-3709 (CVE-2026-64561)
Vulnerability from osv_openeuler – Published: 2026-09-14 16:33 – Updated: 2026-09-14 16:33 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Check for invalid/obsolete root after making MMU pages available\n\nCheck for a \"stale\" page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is \"fine\", but because child shadow pages inherit their parent's role, any children created during the map/fetch will be created as invalid pages, thus violating KVM's invariant that invalid pages are never on the list of active MMU pages.\n\nNote, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, \"KVM: MMU: ignore zapped root pagetables\"), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can't be on the list of active pages.\n\nNote #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.(CVE-2026-64561)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"bpftool-debuginfo-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-64k-6.6.0-159.4.13.167.oe2403sp4+64k.aarch64.rpm",
"kernel-64k-devel-6.6.0-159.4.13.167.oe2403sp4+64k.aarch64.rpm",
"kernel-64k-extra-modules-6.6.0-159.4.13.167.oe2403sp4+64k.aarch64.rpm",
"kernel-64k-source-6.6.0-159.4.13.167.oe2403sp4+64k.aarch64.rpm",
"kernel-debuginfo-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-debugsource-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-devel-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-extra-modules-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-headers-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-source-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-tools-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-tools-debuginfo-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"kernel-tools-devel-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"perf-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"perf-debuginfo-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"python3-perf-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm",
"python3-perf-debuginfo-6.6.0-159.4.13.167.oe2403sp4.aarch64.rpm"
],
"src": [
"kernel-6.6.0-159.4.13.167.oe2403sp4.src.rpm"
],
"x86_64": [
"bpftool-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"bpftool-debuginfo-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-debuginfo-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-debugsource-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-devel-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-extra-modules-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-headers-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-source-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-tools-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-tools-debuginfo-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"kernel-tools-devel-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"perf-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"perf-debuginfo-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"python3-perf-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm",
"python3-perf-debuginfo-6.6.0-159.4.13.167.oe2403sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-24.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.6.0-159.4.13.167.oe2403sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: x86: Check for invalid/obsolete root *after* making MMU pages available\\n\\nCheck for a \\\u0026quot;stale\\\u0026quot; page fault, i.e. for an invalid and/or obsolete root, after making MMU pages available for the shadow MMU. If reclaiming shadow pages zaps an in-use root, i.e. marks it invalid, then KVM will attempt to map memory into an invalid root. On its own, populating an invalid root is \\\u0026quot;fine\\\u0026quot;, but because child shadow pages inherit their parent\u0026apos;s role, any children created during the map/fetch will be created as invalid pages, thus violating KVM\u0026apos;s invariant that invalid pages are never on the list of active MMU pages.\\n\\nNote, the underlying flaw has existed since KVM first started tracking invalid roots in 2008 (commit 2e53d63acba7, \\\u0026quot;KVM: MMU: ignore zapped root pagetables\\\u0026quot;), but the true badness only came along in 2020 (Linux 5.9) with the invariant that invalid shadow pages can\u0026apos;t be on the list of active pages.\\n\\nNote #2, inheriting role.invalid when creating child shadow pages is also far from ideal; that flaw will be addressed separately.(CVE-2026-64561)",
"id": "OESA-2026-3709",
"modified": "2026-09-14T16:33:36Z",
"published": "2026-09-14T16:33:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3709"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64561"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2026-64561"
]
}
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.