GHSA-C768-P8F4-45MG
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: nv: Fix null ptr deref on nested wp/unmap, teardown race
Commit 7270cc9157f4 ("KVM: arm64: nv: Handle VNCR_EL2 invalidation from MMU notifiers") introduced VNCR_EL2 invalidation in both kvm_nested_s2_unmap() and kvm_nested_s2_wp().
However at the point of this being performed concurrent stage 2 teardown of a nested guest can cause kvm->arch.mmu.pgt to be set to NULL.
This happens in kvm_flush_shadow_all() -> kvm_arch_flush_shadow_all() -> kvm_free_stage2_pgd() and is performed under the kvm->mmu_lock.
Commit ec14c272408a ("KVM: arm64: nv: Unmap/flush shadow stage 2 page tables") introduced the teardown of the entire nested MMU range, which then invokes stage2_apply_range() with resched=true:
mmu_notifier_invalidate_range_start() -> ... -> kvm_mmu_notifier_invalidate_range_start() -> kvm_mmu_unmap_gfn_range() -> kvm_unmap_gfn_range() -> kvm_nested_s2_unmap() -> kvm_stage2_unmap_range() -> __unmap_stage2_range() -> stage2_apply_range()
This means that stage2_apply_range() can drop the kvm->mmu_lock and thus concurrent progress can be made in lockstep with kvm_arch_flush_shadow_all().
If kvm_arch_flush_shadow_all() advances ahead of stage2_apply_range() and completes its operation it guarantees a NULL pointer deref.
Since kvm_free_stage2_pgd() is performed under the kvm->mmu_lock this will either be observed NULL or not and serialised against kvm_free_stage2_pgd().
Resolve the issue by abstracting the invalidation to a new function, kvm_invalidate_vncr_ipa_all(), and check that the pgt is non-NULL before dereferencing it.
{
"affected": [],
"aliases": [
"CVE-2026-98467"
],
"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: nv: Fix null ptr deref on nested wp/unmap, teardown race\n\nCommit 7270cc9157f4 (\"KVM: arm64: nv: Handle VNCR_EL2 invalidation from MMU\nnotifiers\") introduced VNCR_EL2 invalidation in both kvm_nested_s2_unmap()\nand kvm_nested_s2_wp().\n\nHowever at the point of this being performed concurrent stage 2 teardown of\na nested guest can cause kvm-\u003earch.mmu.pgt to be set to NULL.\n\nThis happens in kvm_flush_shadow_all() -\u003e kvm_arch_flush_shadow_all() -\u003e\nkvm_free_stage2_pgd() and is performed under the kvm-\u003emmu_lock.\n\nCommit ec14c272408a (\"KVM: arm64: nv: Unmap/flush shadow stage 2 page\ntables\") introduced the teardown of the entire nested MMU range, which then\ninvokes stage2_apply_range() with resched=true:\n\nmmu_notifier_invalidate_range_start()\n -\u003e ... -\u003e kvm_mmu_notifier_invalidate_range_start()\n -\u003e kvm_mmu_unmap_gfn_range()\n -\u003e kvm_unmap_gfn_range()\n -\u003e kvm_nested_s2_unmap()\n -\u003e kvm_stage2_unmap_range()\n -\u003e __unmap_stage2_range()\n -\u003e stage2_apply_range()\n\nThis means that stage2_apply_range() can drop the kvm-\u003emmu_lock and thus\nconcurrent progress can be made in lockstep with\nkvm_arch_flush_shadow_all().\n\nIf kvm_arch_flush_shadow_all() advances ahead of stage2_apply_range() and\ncompletes its operation it guarantees a NULL pointer deref.\n\nSince kvm_free_stage2_pgd() is performed under the kvm-\u003emmu_lock this will\neither be observed NULL or not and serialised against\nkvm_free_stage2_pgd().\n\nResolve the issue by abstracting the invalidation to a new function,\nkvm_invalidate_vncr_ipa_all(), and check that the pgt is non-NULL before\ndereferencing it.",
"id": "GHSA-c768-p8f4-45mg",
"modified": "2026-10-18T18:31:50Z",
"published": "2026-10-18T18:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98467"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3cefc1ab511fad6a0f708e7a4aee9f91346e9457"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4c74e233cdedd11592775fae2a6243e67ca3f891"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/970de111c087488e53cadf5480b94e0f695db985"
}
],
"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.