CVE-2026-89796: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-q9wh-9494-vg25
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89796
GHSA Identifier GHSA-q9wh-9494-vg25
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-89796

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-89796, 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: mm/damon/core: avoid infinite kdamond_merge_regions() internal loop Patch series "mm/damon: unurgent fixes for infinite loop, NULL de-ref and races", v1.1. Sashiko found a few issues in DAMON that could cause infinite loop, NULL dereference and monitoring results degradation. The first two sounds scary but the infinite loop happens only under unreasonable user setup. The NULL dereference is only in a unit test. Monitoring results degradation is trivial since it is only best-effort, and those happens from only unlikely races. Still those are bugs that better to fix if possible. Fix those. This patch (of 6): Due to online parameter update like events, the number of DAMON regions could be higher than the user-set upper limit. kdamond_merge_regions() repeats merge regions until the number meets the limit, while doubling the merge threshold up to the theoretical maximum threshold. It is tried only up to the theoretical maximum threshold because even the aggressive merging can fail from reducing the number of regions under the user-defined upper limit. For example, there could be many user-defined non-contiguous regions that cannot be merged. The threshold based loop break condition is evaluated by comparing the threshold for the next merging try against the theoretical maximum threshold. If max_thres is larger than UINT_MAX / 2, doubling the threshold could make it overflow, and bypass the loop break condition. In the case, if the number of regions cannot be reduced under the upper limit like explained above, the loop will run infinitely. Prevent the case by doing the break condition check before doubling the threshold. Also, prevent the threshold exceeding the maximum threshold, as it could overflow and apply the wrong merge threshold. This issue is unlikely to occur in real world, since having the max_thres higher than UINT_MAX / 2 require unrealistically large aggregation intervals compared to the sampling interval. Also, it requires an unrealistically large number of uncontiguous regions setup. Nonetheless, the consequence is bad and the fix is simple. The issue was discovered [1] by Sashiko.

References

NVD — CVE-2026-89796 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89796
git.kernel.org/stable/c/123e4619ab... WEB
https://git.kernel.org/stable/c/123e4619ab6c8ab1c4cb1d7a58311a2af13929cd
git.kernel.org/stable/c/407da1dd7f... WEB
https://git.kernel.org/stable/c/407da1dd7f48e5ba22ceb8834f6923390632d025
git.kernel.org/stable/c/50a7a5aec1... WEB
https://git.kernel.org/stable/c/50a7a5aec1aa43efc297fd4377c1cbdc7d15620d
git.kernel.org/stable/c/5b0953f86d... WEB
https://git.kernel.org/stable/c/5b0953f86d65855dc901050f40bbe6da0475d198
git.kernel.org/stable/c/65edd8b3a8... WEB
https://git.kernel.org/stable/c/65edd8b3a88278c9f8e5c7d8c15d4f296ce35078
git.kernel.org/stable/c/769c16699c... WEB
https://git.kernel.org/stable/c/769c16699c89811386eb003c8fd9dcb8d405b316
git.kernel.org/stable/c/8a96a06e04... WEB
https://git.kernel.org/stable/c/8a96a06e04d210845be5d9581c0e9e338947e8f8

Frequently Asked Questions

What is CVE-2026-89796?
CVE-2026-89796 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-89796?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89796?
CVE-2026-89796 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89796?
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-q9wh-9494-vg25",
  "modified" : "2026-10-03T12:31:07Z",
  "published" : "2026-09-16T12:30:35Z",
  "aliases" : [ "CVE-2026-89796" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: avoid infinite kdamond_merge_regions() internal loop\n\nPatch series \"mm/damon: unurgent fixes for infinite loop, NULL de-ref and\nraces\", v1.1.\n\nSashiko found a few issues in DAMON that could cause infinite loop, NULL\ndereference and monitoring results degradation.  The first two sounds\nscary but the infinite loop happens only under unreasonable user setup. \nThe NULL dereference is only in a unit test.  Monitoring results\ndegradation is trivial since it is only best-effort, and those happens\nfrom only unlikely races.  Still those are bugs that better to fix if\npossible.  Fix those.\n\n\nThis patch (of 6):\n\nDue to online parameter update like events, the number of DAMON regions\ncould be higher than the user-set upper limit.  kdamond_merge_regions()\nrepeats merge regions until the number meets the limit, while doubling the\nmerge threshold up to the theoretical maximum threshold.  It is tried only\nup to the theoretical maximum threshold because even the aggressive\nmerging can fail from reducing the number of regions under the\nuser-defined upper limit.  For example, there could be many user-defined\nnon-contiguous regions that cannot be merged.\n\nThe threshold based loop break condition is evaluated by comparing the\nthreshold for the next merging try against the theoretical maximum\nthreshold.  If max_thres is larger than UINT_MAX / 2, doubling the\nthreshold could make it overflow, and bypass the loop break condition.  In\nthe case, if the number of regions cannot be reduced under the upper limit\nlike explained above, the loop will run infinitely.\n\nPrevent the case by doing the break condition check before doubling the\nthreshold.  Also, prevent the threshold exceeding the maximum threshold,\nas it could overflow and apply the wrong merge threshold.\n\nThis issue is unlikely to occur in real world, since having the max_thres\nhigher than UINT_MAX / 2 require unrealistically large aggregation\nintervals compared to the sampling interval.  Also, it requires an\nunrealistically large number of uncontiguous regions setup.  Nonetheless,\nthe consequence is bad and the fix is simple.\n\nThe issue was discovered [1] by Sashiko.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89796"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/123e4619ab6c8ab1c4cb1d7a58311a2af13929cd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/407da1dd7f48e5ba22ceb8834f6923390632d025"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/50a7a5aec1aa43efc297fd4377c1cbdc7d15620d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5b0953f86d65855dc901050f40bbe6da0475d198"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/65edd8b3a88278c9f8e5c7d8c15d4f296ce35078"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/769c16699c89811386eb003c8fd9dcb8d405b316"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8a96a06e04d210845be5d9581c0e9e338947e8f8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:16:44Z"
  }
}