CVE-2026-89759: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-cr6x-j7pj-fq6g
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89759
GHSA Identifier GHSA-cr6x-j7pj-fq6g
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-89759

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-89759, 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/kmemleak: avoid soft lockup when scanning task stacks Patch series "mm/kmemleak: avoid soft lockup when scanning task", v3. kmemleak_scan() scans every task stack under one rcu_read_lock() with no reschedule point, which can trip the soft lockup watchdog on hosts with very many threads. That prints the following message, depending on the workload+host configuration: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread Patch 1 walks the tasks with find_ge_pid() so the scan reschedules between tasks Patches 2-3 let the scan loops stop early once a scan is interrupted. This patch (of 3): kmemleak_scan() walks every thread and scans its kernel stack under a single rcu_read_lock() with no reschedule point. On a host with very many threads -- amplified by KASAN/lockdep in debug builds -- this loop can hog a CPU long enough to trip the soft lockup watchdog: watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537] scan_block kmemleak_scan kmemleak_scan_thread kthread A cond_resched() cannot be added directly: the loop runs inside an RCU read-side critical section. Walk the tasks one PID at a time with find_ge_pid(), taking the RCU read lock only to look up and pin each task. The stack is then scanned with no lock held, so cond_resched() runs between tasks and the scan stops early on scan_should_stop(). This follows the next_tgid()/task_seq_get_next() iteration pattern and keeps each RCU critical section short.

References

NVD — CVE-2026-89759 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89759
git.kernel.org/stable/c/1838c704bc... WEB
https://git.kernel.org/stable/c/1838c704bcb4fd3556cf67513c6f97a39099e35c
git.kernel.org/stable/c/3fc8044251... WEB
https://git.kernel.org/stable/c/3fc8044251de21555fb02c365fa681bab8b0db55
git.kernel.org/stable/c/5d10d4e19e... WEB
https://git.kernel.org/stable/c/5d10d4e19e6daa487f0cd0ea6cba472325de92f9
git.kernel.org/stable/c/9a1b12c06c... WEB
https://git.kernel.org/stable/c/9a1b12c06c192290b8479de48f66f1e75d89c4b7

Frequently Asked Questions

What is CVE-2026-89759?
CVE-2026-89759 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-89759?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89759?
CVE-2026-89759 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89759?
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-cr6x-j7pj-fq6g",
  "modified" : "2026-09-11T21:31:39Z",
  "published" : "2026-09-11T21:31:39Z",
  "aliases" : [ "CVE-2026-89759" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/kmemleak: avoid soft lockup when scanning task stacks\n\nPatch series \"mm/kmemleak: avoid soft lockup when scanning task\", v3.\n\nkmemleak_scan() scans every task stack under one rcu_read_lock() with no\nreschedule point, which can trip the soft lockup watchdog on hosts with\nvery many threads.\n\nThat prints the following message, depending on the workload+host\nconfiguration:\n\n      watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537]\n       scan_block\n       kmemleak_scan\n       kmemleak_scan_thread\n       kthread\n\nPatch 1 walks the tasks with find_ge_pid() so the scan reschedules between\ntasks\n\nPatches 2-3 let the scan loops stop early once a scan is interrupted.\n\n\nThis patch (of 3):\n\nkmemleak_scan() walks every thread and scans its kernel stack under a\nsingle rcu_read_lock() with no reschedule point.  On a host with very many\nthreads -- amplified by KASAN/lockdep in debug builds -- this loop can hog\na CPU long enough to trip the soft lockup watchdog:\n\n  watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [kmemleak:537]\n   scan_block\n   kmemleak_scan\n   kmemleak_scan_thread\n   kthread\n\nA cond_resched() cannot be added directly: the loop runs inside an RCU\nread-side critical section.\n\nWalk the tasks one PID at a time with find_ge_pid(), taking the RCU read\nlock only to look up and pin each task.  The stack is then scanned with no\nlock held, so cond_resched() runs between tasks and the scan stops early\non scan_should_stop().  This follows the next_tgid()/task_seq_get_next()\niteration pattern and keeps each RCU critical section short.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89759"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1838c704bcb4fd3556cf67513c6f97a39099e35c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3fc8044251de21555fb02c365fa681bab8b0db55"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5d10d4e19e6daa487f0cd0ea6cba472325de92f9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a1b12c06c192290b8479de48f66f1e75d89c4b7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:06Z"
  }
}