CVE-2026-98717: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-hf2p-vjqm-2xw6
Share
Published
Advisory Summary

CVE-2026-98717 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98717 at a Glance

CVE Identifier CVE-2026-98717
GHSA Identifier GHSA-hf2p-vjqm-2xw6
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98717

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98717, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Bail from shadow walks if the root is invalid or a dummy When walking shadow page tables, immediately terminate the walk if the root is a "dummy" root, i.e. a root whose top-level page table is backed by the zero page, but otherwise doesn't exist. If memslot creation races with a stage-2 page fault (EPT violation or #NPF) from L2, then if the stars align, KVM will attempt to walk shadow page tables using the zero page and hit a NULL pointer deref. BUG: kernel NULL pointer dereference, address: 0000000000000021 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP CPU: 30 UID: 1000 PID: 941 Comm: qemu Not tainted 7.2.0-rc2-1b731e5ded48-next-vm #1741 PREEMPTLAZY Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:__kvm_mmu_invalidate_addr+0xea/0x210 [kvm] Call Trace: <TASK> kvm_mmu_invalidate_addr+0x92/0xe0 [kvm] __kvm_inject_emulated_page_fault+0x67/0x80 [kvm] ept_page_fault+0x160/0x850 [kvm] kvm_mmu_do_page_fault+0x102/0x1f0 [kvm] kvm_mmu_page_fault+0x8e/0x6b0 [kvm] vmx_handle_exit+0x163/0x640 [kvm_intel] kvm_arch_vcpu_ioctl_run+0x960/0x2120 [kvm] kvm_vcpu_ioctl+0x2c7/0x970 [kvm] __x64_sys_ioctl+0x90/0xd0 do_syscall_64+0x67/0x5f0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f606d0b53bb Opportunistically harden the shadow walks against fully invalid roots, but WARN, as all callers are expected/required to pre-check for a valid root. Don't WARN in the dummy root case as the whole point of using a dummy root is to provide a root that's valid enough to enter the guest, i.e. it should Just Work for all flows except those that *need* to know about dummy roots. Alternatively, KVM could allocate a dedicated page and associated shadow page structure for the dummy root, which is very tempting as it such an approach should be more resilient against unexpected behavior. But that would be a much larger and thus riskier change than simply terminating walks of dummy roots.

References

NVD — CVE-2026-98717 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98717
git.kernel.org/stable/c/681e31f03e... WEB
https://git.kernel.org/stable/c/681e31f03ec9219099a66a0f6e1bc48e1b5aa914
git.kernel.org/stable/c/97c1dcce17... WEB
https://git.kernel.org/stable/c/97c1dcce17ef27853860c781f9912257e6adbf7c
git.kernel.org/stable/c/b6249c1d56... WEB
https://git.kernel.org/stable/c/b6249c1d5665098c8bf12f8d3e4712bf04c775bc
git.kernel.org/stable/c/e1bcabc07e... WEB
https://git.kernel.org/stable/c/e1bcabc07efd029ab414894127411129ffdb8b48

Frequently Asked Questions

What is CVE-2026-98717?
CVE-2026-98717 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98717?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98717?
CVE-2026-98717 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98717?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hf2p-vjqm-2xw6",
  "modified" : "2026-10-18T18:32:00Z",
  "published" : "2026-10-18T18:32:00Z",
  "aliases" : [ "CVE-2026-98717" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Bail from shadow walks if the root is invalid or a dummy\n\nWhen walking shadow page tables, immediately terminate the walk if the root\nis a \"dummy\" root, i.e. a root whose top-level page table is backed by the\nzero page, but otherwise doesn't exist.  If memslot creation races with a\nstage-2 page fault (EPT violation or #NPF) from L2, then if the stars align,\nKVM will attempt to walk shadow page tables using the zero page and hit a\nNULL pointer deref.\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000021\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 30 UID: 1000 PID: 941 Comm: qemu Not tainted 7.2.0-rc2-1b731e5ded48-next-vm #1741 PREEMPTLAZY\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:__kvm_mmu_invalidate_addr+0xea/0x210 [kvm]\n  Call Trace:\n   <TASK>\n   kvm_mmu_invalidate_addr+0x92/0xe0 [kvm]\n   __kvm_inject_emulated_page_fault+0x67/0x80 [kvm]\n   ept_page_fault+0x160/0x850 [kvm]\n   kvm_mmu_do_page_fault+0x102/0x1f0 [kvm]\n   kvm_mmu_page_fault+0x8e/0x6b0 [kvm]\n   vmx_handle_exit+0x163/0x640 [kvm_intel]\n   kvm_arch_vcpu_ioctl_run+0x960/0x2120 [kvm]\n   kvm_vcpu_ioctl+0x2c7/0x970 [kvm]\n   __x64_sys_ioctl+0x90/0xd0\n   do_syscall_64+0x67/0x5f0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f606d0b53bb\n\nOpportunistically harden the shadow walks against fully invalid roots, but\nWARN, as all callers are expected/required to pre-check for a valid root.\nDon't WARN in the dummy root case as the whole point of using a dummy root\nis to provide a root that's valid enough to enter the guest, i.e. it should\nJust Work for all flows except those that *need* to know about dummy roots.\n\nAlternatively, KVM could allocate a dedicated page and associated shadow\npage structure for the dummy root, which is very tempting as it such an\napproach should be more resilient against unexpected behavior.  But that\nwould be a much larger and thus riskier change than simply terminating\nwalks of dummy roots.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98717"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/681e31f03ec9219099a66a0f6e1bc48e1b5aa914"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/97c1dcce17ef27853860c781f9912257e6adbf7c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b6249c1d5665098c8bf12f8d3e4712bf04c775bc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e1bcabc07efd029ab414894127411129ffdb8b48"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:25Z"
  }
}