CVE-2026-89991: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-c23v-6rx9-2699
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-89991
GHSA Identifier GHSA-c23v-6rx9-2699
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-89991

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-89991, 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: bpf: Fix infinite loop in pcpu_freelist push with one possible CPU __pcpu_freelist_push() can loop forever when only one CPU is possible and an NMI re-enters pcpu_freelist_push() while the interrupted context holds that CPU's freelist lock. After the current-CPU fast path fails, the fallback loop walks cpu_possible_mask while skipping the current CPU. With CONFIG_SMP=n, or when an SMP kernel is limited to one possible CPU with nr_cpus=1 or possible_cpus=1, there are no other possible CPUs to examine. The loop therefore makes no lock acquisition attempt and can never make progress. The following stack was observed on a UP system: NMI context: pcpu_freelist_push free_htab_elem htab_map_delete_elem [perf-event BPF program] __perf_event_overflow perf_event_nmi_handler exc_nmi Interrupted context: __pcpu_freelist_push pcpu_freelist_push free_htab_elem htab_map_delete_elem [raw_tp/sys_enter BPF program] __bpf_trace_sys_enter do_syscall_64 raw_res_spin_lock() detects the same-CPU recursive acquisition and returns -EDEADLK, but the subsequent fallback loop has no candidate head on a system with one possible CPU. Restore the extra fallback head that existed before the rqspinlock conversion. Keep the current-CPU fast path, then try the other possible CPUs and finally the extra head. The additional head lets a push, which cannot fail without losing a preallocated element, make progress when the only per-CPU head is held by the interrupted context. Also check the extra head from the pop path so that nodes placed there can be reused.

References

NVD — CVE-2026-89991 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89991
git.kernel.org/stable/c/a24a146ae2... WEB
https://git.kernel.org/stable/c/a24a146ae2cb5d9faeea96d10010fcb6579abe1f
git.kernel.org/stable/c/a5b5e62bac... WEB
https://git.kernel.org/stable/c/a5b5e62baceff9e252c6535cf42a027d04f226cf
git.kernel.org/stable/c/efebf64966... WEB
https://git.kernel.org/stable/c/efebf6496685c93150df5bb0794363ae70c5f58a

Frequently Asked Questions

What is CVE-2026-89991?
CVE-2026-89991 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-89991?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89991?
CVE-2026-89991 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89991?
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-c23v-6rx9-2699",
  "modified" : "2026-09-16T12:30:44Z",
  "published" : "2026-09-16T12:30:44Z",
  "aliases" : [ "CVE-2026-89991" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix infinite loop in pcpu_freelist push with one possible CPU\n\n__pcpu_freelist_push() can loop forever when only one CPU is possible\nand an NMI re-enters pcpu_freelist_push() while the interrupted context\nholds that CPU's freelist lock.\n\nAfter the current-CPU fast path fails, the fallback loop walks\ncpu_possible_mask while skipping the current CPU. With CONFIG_SMP=n, or\nwhen an SMP kernel is limited to one possible CPU with nr_cpus=1 or\npossible_cpus=1, there are no other possible CPUs to examine. The loop\ntherefore makes no lock acquisition attempt and can never make progress.\n\nThe following stack was observed on a UP system:\n\n  NMI context:\n    pcpu_freelist_push\n    free_htab_elem\n    htab_map_delete_elem\n    [perf-event BPF program]\n    __perf_event_overflow\n    perf_event_nmi_handler\n    exc_nmi\n\n  Interrupted context:\n    __pcpu_freelist_push\n    pcpu_freelist_push\n    free_htab_elem\n    htab_map_delete_elem\n    [raw_tp/sys_enter BPF program]\n    __bpf_trace_sys_enter\n    do_syscall_64\n\nraw_res_spin_lock() detects the same-CPU recursive acquisition and\nreturns -EDEADLK, but the subsequent fallback loop has no candidate head\non a system with one possible CPU.\n\nRestore the extra fallback head that existed before the rqspinlock\nconversion. Keep the current-CPU fast path, then try the other possible\nCPUs and finally the extra head. The additional head lets a push, which\ncannot fail without losing a preallocated element, make progress when the\nonly per-CPU head is held by the interrupted context.\n\nAlso check the extra head from the pop path so that nodes placed there\ncan be reused.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89991"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a24a146ae2cb5d9faeea96d10010fcb6579abe1f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a5b5e62baceff9e252c6535cf42a027d04f226cf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/efebf6496685c93150df5bb0794363ae70c5f58a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:10Z"
  }
}