CVE-2026-97921: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-v583-2w7f-r9gc
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-97921
GHSA Identifier GHSA-v583-2w7f-r9gc
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-97921

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-97921, 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: Free histogram the field rejected for a bad modifier Writing a hist trigger whose value or variable carries a modifier that is not allowed there leaks the fields that were built for it. __create_val_field() takes the field from parse_expr() and stores it in hist_data->fields[] only after the modifier checks have run: hist_field = parse_expr(hist_data, file, field_str, flags, var_name, &n_subexprs); ... if (hist_field->flags & HIST_FIELD_FL_VAR) { if (hist_field->flags & (...)) goto err; } else { if (hist_field->flags & (...)) goto err; } hist_data->fields[val_idx] = hist_field; Both checks jump past that store, and the err label returns without freeing anything. The error unwinds to create_hist_data(), which calls destroy_hist_data() -> destroy_hist_fields(), and that reaches a field only by walking fields[]. A field that never got there is unreachable. commit e0213434fe3e ("tracing: Do not let histogram values have some modifiers") set ret to -EINVAL and fell through to the store, which left the field owned by fields[] and freed along with the rest of hist_data. Splitting the check into a value case and a variable case replaced that fall-through with a goto that skips it. With CONFIG_DEBUG_KMEMLEAK, 200 writes of # echo 'hist:keys=prev_pid:vals=next_pid.log2' > \ events/sched/sched_switch/trigger each correctly rejected with -EINVAL, leave 332 unreferenced objects (63744 bytes) reported at create_hist_field(); 200 install and remove cycles of a valid trigger leave none. A '.log2' field is two allocations, since create_hist_field() puts the plain field in operands[0] of the log2 field, and both are reported. Use destroy_hist_field() rather than __destroy_hist_field() so that operands[0] is freed as well. It returns early for HIST_FIELD_FL_VAR_REF, which is what an operand owned by hist_data->var_refs[] needs; the rejected field itself is never a var ref, because a var ref never carries a modifier flag.

References

NVD — CVE-2026-97921 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97921
git.kernel.org/stable/c/230234d12c... WEB
https://git.kernel.org/stable/c/230234d12ce42ab04132a32c3a848f07a5d27a71
git.kernel.org/stable/c/3d42fed18b... WEB
https://git.kernel.org/stable/c/3d42fed18b2c5707b6332ebe87b789fd768eb01b
git.kernel.org/stable/c/891c21f6d5... WEB
https://git.kernel.org/stable/c/891c21f6d5673b2a519b536243bfc6dd2d35beb6
git.kernel.org/stable/c/a2652fcf96... WEB
https://git.kernel.org/stable/c/a2652fcf96b63e9da04951e4e58e6a0672df695d
git.kernel.org/stable/c/b22dc0add7... WEB
https://git.kernel.org/stable/c/b22dc0add7d72b8bd9cae3188db0dd65da1c8652
git.kernel.org/stable/c/e787361bb6... WEB
https://git.kernel.org/stable/c/e787361bb6b0026ea3eb4d3fa7a304c7fcb99555

Frequently Asked Questions

What is CVE-2026-97921?
CVE-2026-97921 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-97921?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-97921?
CVE-2026-97921 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-97921?
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-v583-2w7f-r9gc",
  "modified" : "2026-10-03T12:31:20Z",
  "published" : "2026-09-25T12:31:28Z",
  "aliases" : [ "CVE-2026-97921" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Free histogram the field rejected for a bad modifier\n\nWriting a hist trigger whose value or variable carries a modifier that is\nnot allowed there leaks the fields that were built for it.\n\n__create_val_field() takes the field from parse_expr() and stores it in\nhist_data->fields[] only after the modifier checks have run:\n\n\thist_field = parse_expr(hist_data, file, field_str, flags, var_name,\n\t\t\t\t&n_subexprs);\n\t...\n\tif (hist_field->flags & HIST_FIELD_FL_VAR) {\n\t\tif (hist_field->flags & (...))\n\t\t\tgoto err;\n\t} else {\n\t\tif (hist_field->flags & (...))\n\t\t\tgoto err;\n\t}\n\n\thist_data->fields[val_idx] = hist_field;\n\nBoth checks jump past that store, and the err label returns without\nfreeing anything. The error unwinds to create_hist_data(), which calls\ndestroy_hist_data() -> destroy_hist_fields(), and that reaches a field\nonly by walking fields[]. A field that never got there is unreachable.\n\ncommit e0213434fe3e (\"tracing: Do not let histogram values have some\nmodifiers\") set ret to -EINVAL and fell through to the store, which left\nthe field owned by fields[] and freed along with the rest of hist_data.\nSplitting the check into a value case and a variable case replaced that\nfall-through with a goto that skips it.\n\nWith CONFIG_DEBUG_KMEMLEAK, 200 writes of\n\n  # echo 'hist:keys=prev_pid:vals=next_pid.log2' > \\\n\t events/sched/sched_switch/trigger\n\neach correctly rejected with -EINVAL, leave 332 unreferenced objects\n(63744 bytes) reported at create_hist_field(); 200 install and remove\ncycles of a valid trigger leave none. A '.log2' field is two\nallocations, since create_hist_field() puts the plain field in\noperands[0] of the log2 field, and both are reported.\n\nUse destroy_hist_field() rather than __destroy_hist_field() so that\noperands[0] is freed as well. It returns early for HIST_FIELD_FL_VAR_REF,\nwhich is what an operand owned by hist_data->var_refs[] needs; the\nrejected field itself is never a var ref, because a var ref never carries\na modifier flag.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97921"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/230234d12ce42ab04132a32c3a848f07a5d27a71"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3d42fed18b2c5707b6332ebe87b789fd768eb01b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/891c21f6d5673b2a519b536243bfc6dd2d35beb6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a2652fcf96b63e9da04951e4e58e6a0672df695d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b22dc0add7d72b8bd9cae3188db0dd65da1c8652"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e787361bb6b0026ea3eb4d3fa7a304c7fcb99555"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:19Z"
  }
}