CVE-2026-89521: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-2jj9-3xxj-4v43
Share
CVSS 7.3
Published
Advisory Summary

CVE-2026-89521 is a HIGH (CVSS 7.3) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89521 at a Glance

CVE Identifier CVE-2026-89521
GHSA Identifier GHSA-2jj9-3xxj-4v43
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.3

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:H/I:L/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 High (C:H)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2026-89521

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-89521, 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: sched/core: Handle pick_task() releasing the rq lock Core scheduling's pick_next_task() breaks when a ->pick_task() implementation can release the rq lock. The selection state derived on entry is only valid while the lock is held continuously. Once a pick can drop the lock, an interleaving selection can invalidate all of it: the single-CPU fast path can commit an uncookied pick although the core went cookied during the release, and forceidle committed by the interleaving selection skews the restarted pass's accounting. Fix it by restarting the whole selection when a pick returns RETRY_TASK after releasing the lock: a single restart point above the state derivation replaces the per-loop restart labels, so a retry picks up state committed by interleaving selections and accounts and resets forceidle like a fresh selection would. need_sync and fi_before latch across retries. Clock validity can't be re-derived - there is no program-ordered way to tell whether the own and core rq clocks are still updated after the lock was released, as other lockers' pin cycles may or may not have invalidated them. When restarting, clear core_clock_updated so that the sibling loop re-updates the core rq, and update the own rq clock if invalidated.

References

NVD — CVE-2026-89521 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89521
git.kernel.org/stable/c/88ed5a6646... WEB
https://git.kernel.org/stable/c/88ed5a66467ca2a5148b9997af9c71d8c43060ad
git.kernel.org/stable/c/c10b216a07... WEB
https://git.kernel.org/stable/c/c10b216a072ff5c57bc880a05f87eb519aecc529

Frequently Asked Questions

What is CVE-2026-89521?
CVE-2026-89521 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-89521?
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-89521?
CVE-2026-89521 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H.
What CWE is associated with CVE-2026-89521?
CVE-2026-89521 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89521?
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-2jj9-3xxj-4v43",
  "modified" : "2026-09-13T09:32:16Z",
  "published" : "2026-09-11T21:31:30Z",
  "aliases" : [ "CVE-2026-89521" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/core: Handle pick_task() releasing the rq lock\n\nCore scheduling's pick_next_task() breaks when a ->pick_task()\nimplementation can release the rq lock. The selection state derived on entry\nis only valid while the lock is held continuously. Once a pick can drop the\nlock, an interleaving selection can invalidate all of it: the single-CPU\nfast path can commit an uncookied pick although the core went cookied during\nthe release, and forceidle committed by the interleaving selection skews the\nrestarted pass's accounting.\n\nFix it by restarting the whole selection when a pick returns RETRY_TASK\nafter releasing the lock: a single restart point above the state derivation\nreplaces the per-loop restart labels, so a retry picks up state committed by\ninterleaving selections and accounts and resets forceidle like a fresh\nselection would.\n\nneed_sync and fi_before latch across retries. Clock validity can't be\nre-derived - there is no program-ordered way to tell whether the own and\ncore rq clocks are still updated after the lock was released, as other\nlockers' pin cycles may or may not have invalidated them. When restarting,\nclear core_clock_updated so that the sibling loop re-updates the core rq,\nand update the own rq clock if invalidated.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89521"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/88ed5a66467ca2a5148b9997af9c71d8c43060ad"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c10b216a072ff5c57bc880a05f87eb519aecc529"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:34Z"
  }
}