CVE-2026-98164: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-4wvx-xqjp-p7g6
Share
CVSS 5.5
CWE-670
Published
Advisory Summary

CVE-2026-98164 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-670: Always-Incorrect Control Flow Implementation) affecting Software libraries in the Maven ecosystem. The weakness occurs when the code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98164 at a Glance

CVE Identifier CVE-2026-98164
GHSA Identifier GHSA-4wvx-xqjp-p7g6
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-670: Always-Incorrect Control Flow Implementation
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-98164

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-98164, 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 CWE-670: Always-Incorrect Control Flow Implementation, where the code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. 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: Check write tracking in all address spaces kvm_gfn_is_write_tracked() checks only the supplied memslot, but page tracking is per-address-space and shadow pages are shared across all address spaces. With SMM, a GFN can therefore be write-tracked in one address space and appear untracked through the other. Check the supplied slot first, then the slot for the other address space. This ensures all callers honor write tracking regardless of the active address space. In particular, it prevents mmu_try_to_unsync_pages() from marking an upper-level shadow page unsync and eventually triggering the BUG in pte_list_remove(). [invert direction of the conditional. - Paolo]

References

NVD — CVE-2026-98164 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98164
git.kernel.org/stable/c/09aa68552d... WEB
https://git.kernel.org/stable/c/09aa68552d2542cc6c23edd1568ac265dc5d886f
git.kernel.org/stable/c/0f38453cdb... WEB
https://git.kernel.org/stable/c/0f38453cdb2e17566ccb7c0f3dabd5bd21caca26
git.kernel.org/stable/c/429b6f43b4... WEB
https://git.kernel.org/stable/c/429b6f43b4d8c98988fdca99e02dc156134e3d77
git.kernel.org/stable/c/c0a9bd5fca... WEB
https://git.kernel.org/stable/c/c0a9bd5fca0b5f2dea32b0fc31350e71e8648112
git.kernel.org/stable/c/d8636c8f9f... WEB
https://git.kernel.org/stable/c/d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a
git.kernel.org/stable/c/ec8fcaf354... WEB
https://git.kernel.org/stable/c/ec8fcaf354c1cbb36755d48e9f5a00c9591349e5

Frequently Asked Questions

What is CVE-2026-98164?
CVE-2026-98164 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-670: Always-Incorrect Control Flow Implementation.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98164?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-98164?
CVE-2026-98164 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-98164?
CVE-2026-98164 is classified under CWE-670: Always-Incorrect Control Flow Implementation (The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated.).
How can I check Maven dependencies for CVE-2026-98164?
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-4wvx-xqjp-p7g6",
  "modified" : "2026-10-02T21:31:57Z",
  "published" : "2026-09-29T15:31:46Z",
  "aliases" : [ "CVE-2026-98164" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Check write tracking in all address spaces\n\nkvm_gfn_is_write_tracked() checks only the supplied memslot, but page\ntracking is per-address-space and shadow pages are shared across all\naddress spaces.  With SMM, a GFN can therefore be write-tracked in one\naddress space and appear untracked through the other.\n\nCheck the supplied slot first, then the slot for the other address space.\nThis ensures all callers honor write tracking regardless of the active\naddress space.  In particular, it prevents mmu_try_to_unsync_pages() from\nmarking an upper-level shadow page unsync and eventually triggering the\nBUG in pte_list_remove().\n\n[invert direction of the conditional. - Paolo]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98164"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/09aa68552d2542cc6c23edd1568ac265dc5d886f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0f38453cdb2e17566ccb7c0f3dabd5bd21caca26"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/429b6f43b4d8c98988fdca99e02dc156134e3d77"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c0a9bd5fca0b5f2dea32b0fc31350e71e8648112"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d8636c8f9f95d0fd1e2f6f1cad0d5757aa6f212a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ec8fcaf354c1cbb36755d48e9f5a00c9591349e5"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-670" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-29T13:17:53Z"
  }
}