CVE-2026-89917: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-crq7-3pj4-2vvg
Published
Advisory Summary

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

CVE Identifier CVE-2026-89917
GHSA Identifier GHSA-crq7-3pj4-2vvg
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-89917

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-89917, 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: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping While VNCR TLB invalidation always occurs under the MMU lock, vcpu_put() doesn't, while it unmaps the VNCR page. The problem is that the invalidation evaluates vncr_tlb::cpu to decide whether an unmapping needs to take place (cpu != -1) before performing it. On the other hand, this_cpu_reset_vncr_fixmap() unconditionally unmaps if L1_VNCR_MAPPED is set. These two obviously can race, with a TOCTOU pattern on the TLBI path, and a BUG_ON() on the vcpu_put() path. And the two can end-up calling vncr_fixmap(-1), with extra lethal effects. Move the reset of vncr_tlb::cpu to -1 to a common function, and make this update atomic so that only a single thread can reset the field and perform the corresponding unmap. The vcpu_put() still need to unconditionally unmap the current VNCR to close another ugly race. Finally, the assignment of vncr_tlb::cpu is moved to be kept in sync with the actual mapping, similar to L1_VNCR_MAPPED being set.

References

Frequently Asked Questions

What is CVE-2026-89917?
CVE-2026-89917 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-89917?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89917?
CVE-2026-89917 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89917?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-crq7-3pj4-2vvg",
  "modified" : "2026-09-16T12:30:41Z",
  "published" : "2026-09-16T12:30:41Z",
  "aliases" : [ "CVE-2026-89917" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Handle VNCR TLB invalidation race with vcpu_put() VNCR unmapping\n\nWhile VNCR TLB invalidation always occurs under the MMU lock,\nvcpu_put() doesn't, while it unmaps the VNCR page.\n\nThe problem is that the invalidation evaluates vncr_tlb::cpu to\ndecide whether an unmapping needs to take place (cpu != -1) before\nperforming it. On the other hand, this_cpu_reset_vncr_fixmap()\nunconditionally unmaps if L1_VNCR_MAPPED is set.\n\nThese two obviously can race, with a TOCTOU pattern on the TLBI\npath, and a BUG_ON() on the vcpu_put() path. And the two can end-up\ncalling vncr_fixmap(-1), with extra lethal effects.\n\nMove the reset of vncr_tlb::cpu to -1 to a common function, and make\nthis update atomic so that only a single thread can reset the field\nand perform the corresponding unmap. The vcpu_put() still need to\nunconditionally unmap the current VNCR to close another ugly race.\n\nFinally, the assignment of vncr_tlb::cpu is moved to be kept in sync\nwith the actual mapping, similar to L1_VNCR_MAPPED being set.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89917"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38640bc32be3fcf9526d477155bc19d3f146231f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5cbd8761d001c11ada73b1753d772c4745a70e72"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9065c1261f8a05c6a7a2d90048c7c0665ab2896d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:00Z"
  }
}