CVE-2026-97936: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7w7w-22gx-h2r2
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97936
GHSA Identifier GHSA-7w7w-22gx-h2r2
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-97936

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-97936, 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: tracing: Fix memory corruption from the histogram stacktrace modifier parse_field() sets HIST_FIELD_FL_STACKTRACE from the ".stacktrace" modifier before it looks the field name up, and nothing afterwards checks that the name resolved to a field which holds a stacktrace. create_hist_field() picks HIST_FIELD_FN_STACK on the strength of the field pointer alone, which reads a __data_loc word from the record and follows its low 16 bits as an offset into the same record. event_hist_trigger() takes the first word there as an entry count and copies that many longs into a 31 entry array: n_entries = *stack; memcpy(entries, ++stack, n_entries * sizeof(unsigned long)); Neither end of that copy is bounded, and the count is whatever the event holds at the offset, so any field will do: # cd /sys/kernel/tracing/events/sched/sched_process_fork # echo 'hist:keys=parent_pid.stacktrace' > trigger # (true) BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:rb_insert_color+0x18/0x130 timerqueue_linked_add+0x7e/0xd0 enqueue_hrtimer+0x39/0xb0 __hrtimer_run_queues+0x10f/0x1f0 </IRQ> RIP: 0010:memcpy+0xc/0x30 event_hist_trigger+0x165/0x690 The timer interrupt landed on the rbtree the copy had already run over. No debug options are needed for this; KASAN reports the same write as an out-of-bounds read of 13835058055416381440 bytes. Documentation/trace/histogram.rst already states the rule, "must be a long[] type", so enforce it once the name has been resolved. Names which resolve to no field at all, "hitcount.stacktrace" and the common_* pseudo-fields, are refused for the same reason: they hold no stacktrace to read.

References

NVD — CVE-2026-97936 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97936
git.kernel.org/stable/c/55caaf25da... WEB
https://git.kernel.org/stable/c/55caaf25da2c2bb9b75307e4c868726cb954b1d6
git.kernel.org/stable/c/57bfc2a179... WEB
https://git.kernel.org/stable/c/57bfc2a17954d173d2a4182f3b582ffbb23aff64
git.kernel.org/stable/c/98da3379cd... WEB
https://git.kernel.org/stable/c/98da3379cdee343f671dac89b9afbd8b071f2591
git.kernel.org/stable/c/a5e70ba87c... WEB
https://git.kernel.org/stable/c/a5e70ba87ca8ebc79b4e63de302d03b0625fe153
git.kernel.org/stable/c/e183b84968... WEB
https://git.kernel.org/stable/c/e183b84968d4a6ea476d806ea97668405aa56880

Frequently Asked Questions

What is CVE-2026-97936?
CVE-2026-97936 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-97936?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97936?
CVE-2026-97936 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97936?
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-7w7w-22gx-h2r2",
  "modified" : "2026-10-03T12:31:21Z",
  "published" : "2026-09-25T12:31:29Z",
  "aliases" : [ "CVE-2026-97936" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Fix memory corruption from the histogram stacktrace modifier\n\nparse_field() sets HIST_FIELD_FL_STACKTRACE from the \".stacktrace\"\nmodifier before it looks the field name up, and nothing afterwards\nchecks that the name resolved to a field which holds a stacktrace.\ncreate_hist_field() picks HIST_FIELD_FN_STACK on the strength of the\nfield pointer alone, which reads a __data_loc word from the record and\nfollows its low 16 bits as an offset into the same record.\nevent_hist_trigger() takes the first word there as an entry count and\ncopies that many longs into a 31 entry array:\n\n\tn_entries = *stack;\n\tmemcpy(entries, ++stack, n_entries * sizeof(unsigned long));\n\nNeither end of that copy is bounded, and the count is whatever the event\nholds at the offset, so any field will do:\n\n  # cd /sys/kernel/tracing/events/sched/sched_process_fork\n  # echo 'hist:keys=parent_pid.stacktrace' > trigger\n  # (true)\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000008\n  RIP: 0010:rb_insert_color+0x18/0x130\n   timerqueue_linked_add+0x7e/0xd0\n   enqueue_hrtimer+0x39/0xb0\n   __hrtimer_run_queues+0x10f/0x1f0\n   </IRQ>\n  RIP: 0010:memcpy+0xc/0x30\n   event_hist_trigger+0x165/0x690\n\nThe timer interrupt landed on the rbtree the copy had already run over.\nNo debug options are needed for this; KASAN reports the same write as an\nout-of-bounds read of 13835058055416381440 bytes.\n\nDocumentation/trace/histogram.rst already states the rule, \"must be a\nlong[] type\", so enforce it once the name has been resolved. Names which\nresolve to no field at all, \"hitcount.stacktrace\" and the common_*\npseudo-fields, are refused for the same reason: they hold no stacktrace\nto read.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97936"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55caaf25da2c2bb9b75307e4c868726cb954b1d6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/57bfc2a17954d173d2a4182f3b582ffbb23aff64"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/98da3379cdee343f671dac89b9afbd8b071f2591"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a5e70ba87ca8ebc79b4e63de302d03b0625fe153"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e183b84968d4a6ea476d806ea97668405aa56880"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:20Z"
  }
}