CVE-2026-97921

tracing: Free histogram the field rejected for a bad modifier

Description

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.

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.211% likely to be exploited in the next 30 days, higher than 11.448% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 7403630eb94c1d664fb873f967427ef2f6ee3699 up to but excluding a2652fcf96b63e9da04951e4e58e6a0672df695d (affected)
  • e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c up to but excluding 3d42fed18b2c5707b6332ebe87b789fd768eb01b (affected)
  • e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c up to but excluding e787361bb6b0026ea3eb4d3fa7a304c7fcb99555 (affected)
  • e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c up to but excluding b22dc0add7d72b8bd9cae3188db0dd65da1c8652 (affected)
  • e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c up to but excluding 891c21f6d5673b2a519b536243bfc6dd2d35beb6 (affected)
  • e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c up to but excluding 230234d12ce42ab04132a32c3a848f07a5d27a71 (affected)
  • 8d505d06d7330f5d67d3e5e9e1c647fb0b10ddad (affected)
  • 6.1.33 up to but excluding 6.1.189 (affected)
  • 6.3.7 up to but excluding 6.4 (affected)
LinuxLinux
  • Default status: affected
  • 6.4 (affected)
  • 0 up to but excluding 6.4 (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References