CVE-2026-89589: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-9wp4-w6jg-245j
Published
Advisory Summary

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

CVE Identifier CVE-2026-89589
GHSA Identifier GHSA-9wp4-w6jg-245j
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-89589

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-89589, 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: acpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks The CXL CPER work registration and unregistration helpers acquire cxl_cper_work_lock and cxl_cper_prot_err_work_lock with a spinlock guard(), which leaves local interrupts enabled. The corresponding post paths (cxl_cper_post_event(), cxl_cper_post_prot_err()) execute in hard IRQ context (they are called from the GHES error notification path) and acquire the same locks with an irqsave guard(). If a CPU is holding one of these locks via a spinlock guard() when a GHES interrupt arrives on the same CPU, the IRQ handler spins on the held lock waiting for it to release, while the lock holder is preempted by the IRQ. The result is a deadlock. Convert both locks from spinlock_t to raw_spinlock_t and use guard() at all call sites. On PREEMPT_RT kernels spinlock_t is backed by rt_mutex and sleeping from hard IRQ context is not permitted; raw_spinlock_t is safe in both contexts. Add WARN_ONCE to both register functions to surface double-registration bugs at runtime. Restructure both unregister functions to clear the global work pointer under the lock before calling cancel_work_sync(), closing the window where a CPER interrupt could schedule work on a pointer about to be freed. Add kfifo_reset() after cancel_work_sync() so stale entries are not replayed on next module load. Both kfifos are single-consumer: only one work_struct is registered at a time, enforced by the WARN_ONCE guard in the register functions. kfifo_reset() is safe outside the lock because cancel_work_sync() has already quiesced the consumer, and no new consumer can register until the current module exit completes and a fresh module init runs. Remove the redundant cancel_work_sync() call from cxl_ras_exit() and cxl_pci_driver_exit(). The CPER unregister functions now quiesce the work internally.

References

Frequently Asked Questions

What is CVE-2026-89589?
CVE-2026-89589 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-89589?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89589?
CVE-2026-89589 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89589?
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-9wp4-w6jg-245j",
  "modified" : "2026-09-21T15:31:36Z",
  "published" : "2026-09-11T21:31:33Z",
  "aliases" : [ "CVE-2026-89589" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nacpi/apei/ghes: Use raw_spinlock_t for CXL CPER work locks\n\nThe CXL CPER work registration and unregistration helpers acquire\ncxl_cper_work_lock and cxl_cper_prot_err_work_lock with a spinlock\nguard(), which leaves local interrupts enabled. The corresponding post\npaths (cxl_cper_post_event(), cxl_cper_post_prot_err()) execute in hard\nIRQ context (they are called from the GHES error notification path) and\nacquire the same locks with an irqsave guard().\n\nIf a CPU is holding one of these locks via a spinlock guard() when a GHES\ninterrupt arrives on the same CPU, the IRQ handler spins on the held lock\nwaiting for it to release, while the lock holder is preempted by the IRQ.\nThe result is a deadlock.\n\nConvert both locks from spinlock_t to raw_spinlock_t and use guard() at\nall call sites. On PREEMPT_RT kernels spinlock_t is backed by rt_mutex and\nsleeping from hard IRQ context is not permitted; raw_spinlock_t is safe in\nboth contexts.\n\nAdd WARN_ONCE to both register functions to surface double-registration\nbugs at runtime.\n\nRestructure both unregister functions to clear the global work pointer\nunder the lock before calling cancel_work_sync(), closing the window\nwhere a CPER interrupt could schedule work on a pointer about to be\nfreed. Add kfifo_reset() after cancel_work_sync() so stale entries\nare not replayed on next module load.\n\nBoth kfifos are single-consumer: only one work_struct is registered at\na time, enforced by the WARN_ONCE guard in the register functions.\nkfifo_reset() is safe outside the lock because cancel_work_sync() has\nalready quiesced the consumer, and no new consumer can register until\nthe current module exit completes and a fresh module init runs.\n\nRemove the redundant cancel_work_sync() call from cxl_ras_exit() and\ncxl_pci_driver_exit(). The CPER unregister functions now quiesce\nthe work internally.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89589"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0e25382b05de48d09b243d3d447d236a6d735bc2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6625ca499c3131ef63be3215f8f942d7a097ea3a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c735dbce7ad03df708bf22ec964f67e43cbc823a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cbc27a4302a1feb0ff77c1755021837a738b0ce9"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:43Z"
  }
}