CVE-2026-89962: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-52p7-4c9h-jcc7
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89962
GHSA Identifier GHSA-52p7-4c9h-jcc7
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-89962

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-89962, 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: powerpc/kexec_file: Prevent kexec range truncation Sashiko AI review pointed out the following issue. The __merge_memory_ranges() function incorrectly handles overlapping memory ranges when merging them. Although sort_memory_ranges() sorts all ranges by their start address in ascending order beforehand, the merge logic remains defective in two ways: 1. It compares the current range's start against the previous element (i-1) instead of the running target index (idx) 2. It unconditionally overwrites 'ranges[idx].end' with 'ranges[i].end'. This logic flaw leads to critical memory truncation when a larger memory range completely subsumes subsequent smaller ranges. For example, consider a sorted input array with three ranges: Range A (idx=0): [0x1000 - 0x9000] Range B (i=1): [0x2000 - 0x5000] (completely inside Range A) Range C (i=2): [0x6000 - 0x8000] (completely inside Range A) 1. When i=1 (Range B): ranges[1].start (0x2000) <= ranges[0].end + 1 (0x9001) is TRUE. The code executes: ranges[0].end = ranges[1].end, which erroneously shrinks Range A's end from 0x9000 down to 0x5000. 2. When i=2 (Range C): ranges[2].start (0x6000) <= ranges[1].end + 1 (0x5001) is FALSE. The code falls into the else block, creating a broken new range. As a result, valid memory fragments [0x5001 - 0x5fff] and [0x8001 - 0x9000] are completely lost from the kexec exclude lists, potentially allowing the crash kernel to overwrite active memory, causing data corruption or crashes. Fix this by ensuring the start of the current range is compared against the end of the active merged range (idx), and use max() to safely prevent the outer boundary from being truncated.

References

NVD — CVE-2026-89962 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89962
git.kernel.org/stable/c/9ef63622e6... WEB
https://git.kernel.org/stable/c/9ef63622e6cee588ea4b763a6afc87065254b36a
git.kernel.org/stable/c/c4cb547f26... WEB
https://git.kernel.org/stable/c/c4cb547f26d9b73b489c5278d0c8db837c5a174f
git.kernel.org/stable/c/da88a2a211... WEB
https://git.kernel.org/stable/c/da88a2a2119e4fd0e8919a7a2448682f574e1545
git.kernel.org/stable/c/fa40f9dbdd... WEB
https://git.kernel.org/stable/c/fa40f9dbdd4af53e7445d9135b5b207eb8adf372

Frequently Asked Questions

What is CVE-2026-89962?
CVE-2026-89962 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-89962?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89962?
CVE-2026-89962 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89962?
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-52p7-4c9h-jcc7",
  "modified" : "2026-09-16T12:30:43Z",
  "published" : "2026-09-16T12:30:43Z",
  "aliases" : [ "CVE-2026-89962" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/kexec_file: Prevent kexec range truncation\n\nSashiko AI review pointed out the following issue.\n\nThe __merge_memory_ranges() function incorrectly handles overlapping\nmemory ranges when merging them. Although sort_memory_ranges() sorts all\nranges by their start address in ascending order beforehand, the merge\nlogic remains defective in two ways:\n\n1. It compares the current range's start against the previous element (i-1)\n   instead of the running target index (idx)\n\n2. It unconditionally overwrites 'ranges[idx].end' with 'ranges[i].end'.\n\nThis logic flaw leads to critical memory truncation when a larger memory\nrange completely subsumes subsequent smaller ranges.\n\nFor example, consider a sorted input array with three ranges:\n  Range A (idx=0): [0x1000 - 0x9000]\n  Range B (i=1):   [0x2000 - 0x5000] (completely inside Range A)\n  Range C (i=2):   [0x6000 - 0x8000] (completely inside Range A)\n\n1. When i=1 (Range B):\n   ranges[1].start (0x2000) <= ranges[0].end + 1 (0x9001) is TRUE.\n   The code executes: ranges[0].end = ranges[1].end, which erroneously\n   shrinks Range A's end from 0x9000 down to 0x5000.\n\n2. When i=2 (Range C):\n   ranges[2].start (0x6000) <= ranges[1].end + 1 (0x5001) is FALSE.\n   The code falls into the else block, creating a broken new range.\n\nAs a result, valid memory fragments [0x5001 - 0x5fff] and [0x8001 - 0x9000]\nare completely lost from the kexec exclude lists, potentially allowing\nthe crash kernel to overwrite active memory, causing data corruption\nor crashes.\n\nFix this by ensuring the start of the current range is compared against the\nend of the active merged range (idx), and use max() to safely prevent the\nouter boundary from being truncated.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89962"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9ef63622e6cee588ea4b763a6afc87065254b36a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c4cb547f26d9b73b489c5278d0c8db837c5a174f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/da88a2a2119e4fd0e8919a7a2448682f574e1545"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fa40f9dbdd4af53e7445d9135b5b207eb8adf372"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:06Z"
  }
}