CVE-2026-97526: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4mg4-96g4-2j54
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97526
GHSA Identifier GHSA-4mg4-96g4-2j54
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-97526

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-97526, 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: s390/pai: Support CPU hotplug for PMU PAI The command 'perf stat -e pai_crypto/CRYPTO_ALL/ -- <command>' crashes the kernel when CPUs are hotplug added during that run. Root cause is the missing allocation of per-CPU data structures for that new CPU. The allocation is dynamic and the first event that has task context creates such a structure for each online CPU. This is not sufficient. CPUs may be offline during event creation and can be set online during the perf run time. For example commands # echo 0 > /sys/devices/system/cpu/cpu1/online # perf stat -e cycles -i -- stress-ng -t10s --matrix X # sleep 1 # echo 1 > /sys/devices/system/cpu/cpu1/online Currently without a CPU hotplug handler, that new CPU has no per-CPU data infrastructure. The scheduler runs PMU call back function pai_add() to install the PMU support for that CPU before the task is being scheduled on that new CPU. In pai_add() instructions mp = this_cpu_ptr(pai_root[idx].mapptr); cpump = mp->mapptr; return a NULL pointer and the result is a kernel panic as variable cpump is used inside that function. Add CPU hotplug support for CPU add and delete and create the necessary per-CPU data infrastructure during CPU hotplug add processing. Same for CPU hotplug remove. This is done when the CPU is offline to ensure the data structures are available when CPU is made online and tasks are scheduled on it. [hca@linux.ibm.com: fixup error path in pai_init()]

References

NVD — CVE-2026-97526 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97526
git.kernel.org/stable/c/706e2bf330... WEB
https://git.kernel.org/stable/c/706e2bf330144995d123dccf32aaf1981ce5abc2
git.kernel.org/stable/c/9ecc4d0338... WEB
https://git.kernel.org/stable/c/9ecc4d033879f7761f2df07e20cd2fbec00fd90b

Frequently Asked Questions

What is CVE-2026-97526?
CVE-2026-97526 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-97526?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97526?
CVE-2026-97526 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97526?
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-4mg4-96g4-2j54",
  "modified" : "2026-09-25T12:31:22Z",
  "published" : "2026-09-25T12:31:22Z",
  "aliases" : [ "CVE-2026-97526" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/pai: Support CPU hotplug for PMU PAI\n\nThe command 'perf stat -e pai_crypto/CRYPTO_ALL/ -- <command>'\ncrashes the kernel when CPUs are hotplug added during that run.\n\nRoot cause is the missing allocation of per-CPU data structures\nfor that new CPU. The allocation is dynamic and the first\nevent that has task context creates such a structure for\neach online CPU. This is not sufficient. CPUs may be offline\nduring event creation and can be set online during the\nperf run time. For example commands\n\n # echo 0 > /sys/devices/system/cpu/cpu1/online\n # perf stat -e cycles -i -- stress-ng -t10s --matrix X\n # sleep 1\n # echo 1 > /sys/devices/system/cpu/cpu1/online\n\nCurrently without a CPU hotplug handler, that new CPU has no\nper-CPU data infrastructure. The scheduler runs PMU call back\nfunction pai_add() to install the PMU support for that CPU before\nthe task is being scheduled on that new CPU.\nIn pai_add() instructions\n\n    mp = this_cpu_ptr(pai_root[idx].mapptr);\n    cpump = mp->mapptr;\n\nreturn a NULL pointer and the result is a kernel panic as variable\ncpump is used inside that function.\n\nAdd CPU hotplug support for CPU add and delete and create\nthe necessary per-CPU data infrastructure during CPU hotplug\nadd processing. Same for CPU hotplug remove.\nThis is done when the CPU is offline to ensure the data structures\nare available when CPU is made online and tasks are scheduled on it.\n\n[hca@linux.ibm.com: fixup error path in pai_init()]",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97526"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/706e2bf330144995d123dccf32aaf1981ce5abc2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9ecc4d033879f7761f2df07e20cd2fbec00fd90b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:02Z"
  }
}