CVE-2026-98468: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-5gcw-m9q3-vcxx
Share
Published
Advisory Summary

CVE-2026-98468 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-98468 at a Glance

CVE Identifier CVE-2026-98468
GHSA Identifier GHSA-5gcw-m9q3-vcxx
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-98468

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-98468, 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: arm64: Fix spurious warning for benign stage 2 teardown race kvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an L2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB of RAM, all of which was then exited. Under memory pressure in the L0 host warnings were observed due to migration triggered by compaction: WARNING: arch/arm64/kvm/mmu.c:336 at __unmap_stage2_range+0x64/0x80, CPU#5: kcompactd0/66 Which was, in turn, triggered by an MMU notifier for the host invalidation: 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() <- -EINVAL, triggering a WARN_ON() Racing with L0's teardown of stage 2 page tables: exit_mm() -> mmput() -> __mmput() -> exit_mmap() -> mmu_notifier_release() -> ... -> kvm_mmu_notifier_release() -> kvm_flush_shadow_all() -> kvm_arch_flush_shadow_all() -> kvm_free_stage2_pgd() -> [ acquire kvm->mmu_lock for write ] -> mmu->pgt = NULL [ among other tasks ] -> [ release kvm->mmu_lock for write ] It turns out there is a benign race resulting in a spurious warning: Thread A - notify: migration | Thread B - notify: release -------------------------------|--------------------------------- < kvm->mmu_lock held > | stage2_apply_range() | get mmu->pgt, check !NULL | ... | kvm_arch_flush_shadow_all() cond_resched_rwlock_write(); | < contend, sleep kvm->mmu_lock > < drop kvm->mmu_lock > | < acquire kvm->mmu_lock> | ... | kvm_free_stage2_pgd() | mmu->pgt = NULL | < invalidate MMU > | ... | < release kvm->mmu_lock > [ scheduled ] | stage2_apply_range() | < loop to next > | get, mmu->pgt, check !NULL | is NULL, return -EINVAL | __unmap_stage2_range() | WARN_ON(-EINVAL) <--- entirely spurious - the race was handled correctly. Fix the spurious warning by updating stage2_apply_range() to no longer treat concurrent PGT teardown on lock release as an error - whether the walker is tearing down page tables or doing something else this is a legitimate reason to abort the operation without error. This keeps the warning in place for all other circumstances. In practice only __unmap_stage2_range() actually does anything with the error so this only impacts that.

References

NVD — CVE-2026-98468 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98468
git.kernel.org/stable/c/330346dda3... WEB
https://git.kernel.org/stable/c/330346dda3bf5f8a3b06723024f7d906326270cf
git.kernel.org/stable/c/38b70fc453... WEB
https://git.kernel.org/stable/c/38b70fc453c3112f1a62583b89903ae41116cc27
git.kernel.org/stable/c/c23ed110d2... WEB
https://git.kernel.org/stable/c/c23ed110d27ba99cf3a881986514f79aacedf476
git.kernel.org/stable/c/f44a926331... WEB
https://git.kernel.org/stable/c/f44a92633136b409ebb9b7036fceb7e11de60a20

Frequently Asked Questions

What is CVE-2026-98468?
CVE-2026-98468 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-98468?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98468?
CVE-2026-98468 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98468?
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-5gcw-m9q3-vcxx",
  "modified" : "2026-10-18T18:31:50Z",
  "published" : "2026-10-18T18:31:50Z",
  "aliases" : [ "CVE-2026-98468" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Fix spurious warning for benign stage 2 teardown race\n\nkvmtool was used to establish an L1 guest with 8 CPUs and 8 GiB of RAM, an\nL2 guest with 4 CPUs and 4 GiB of RAM and an L3 guest with 2 CPUs and 2 GiB\nof RAM, all of which was then exited.\n\nUnder memory pressure in the L0 host warnings were observed due to\nmigration triggered by compaction:\n\nWARNING: arch/arm64/kvm/mmu.c:336 at __unmap_stage2_range+0x64/0x80,\nCPU#5: kcompactd0/66\n\nWhich was, in turn, triggered by an MMU notifier for the host invalidation:\n\nmmu_notifier_invalidate_range_start()\n  -> ... -> kvm_mmu_notifier_invalidate_range_start()\n    -> kvm_mmu_unmap_gfn_range()\n      -> kvm_unmap_gfn_range()\n        -> kvm_nested_s2_unmap()\n          -> kvm_stage2_unmap_range()\n            -> __unmap_stage2_range()\n               -> stage2_apply_range()\n       \t       <- -EINVAL, triggering a WARN_ON()\n\nRacing with L0's teardown of stage 2 page tables:\n\nexit_mm()\n  -> mmput()\n    -> __mmput()\n      -> exit_mmap()\n        -> mmu_notifier_release()\n\t  -> ... -> kvm_mmu_notifier_release()\n            -> kvm_flush_shadow_all()\n              -> kvm_arch_flush_shadow_all()\n\t        -> kvm_free_stage2_pgd()\n\t\t  -> [ acquire kvm->mmu_lock for write ]\n\t\t  -> mmu->pgt = NULL [ among other tasks ]\n\t\t  -> [ release kvm->mmu_lock for write ]\n\nIt turns out there is a benign race resulting in a spurious warning:\n\n\tThread A - notify: migration   | Thread B - notify: release\n\t-------------------------------|---------------------------------\n\t< kvm->mmu_lock held >         |\n\tstage2_apply_range()           |\n\t  get mmu->pgt, check !NULL    |\n\t  ...                          | kvm_arch_flush_shadow_all()\n\t  cond_resched_rwlock_write(); |   < contend, sleep kvm->mmu_lock >\n\t< drop kvm->mmu_lock >         |   < acquire kvm->mmu_lock>\n                                       |   ...\n\t\t\t\t       |   kvm_free_stage2_pgd()\n                                       |     mmu->pgt = NULL\n\t\t\t\t       |   < invalidate MMU >\n\t\t\t\t       |   ...\n\t\t\t\t       |   < release kvm->mmu_lock >\n\t[ scheduled ]\t\t       |\n\tstage2_apply_range()           |\n\t  < loop to next >             |\n\t  get, mmu->pgt, check !NULL   |\n\t  is NULL, return -EINVAL      |\n        __unmap_stage2_range()         |\n\t  WARN_ON(-EINVAL) <--- entirely spurious - the race was handled\n                                 correctly.\n\nFix the spurious warning by updating stage2_apply_range() to no longer\ntreat concurrent PGT teardown on lock release as an error - whether the\nwalker is tearing down page tables or doing something else this is a\nlegitimate reason to abort the operation without error.\n\nThis keeps the warning in place for all other circumstances.\n\nIn practice only __unmap_stage2_range() actually does anything with the\nerror so this only impacts that.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98468"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/330346dda3bf5f8a3b06723024f7d906326270cf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38b70fc453c3112f1a62583b89903ae41116cc27"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c23ed110d27ba99cf3a881986514f79aacedf476"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f44a92633136b409ebb9b7036fceb7e11de60a20"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:16:57Z"
  }
}