CVE-2026-97921: tracing: Free histogram the field rejected for a bad modifier
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 230234d12ce42ab04132a32c3a848f07a5d27a71, 3d42fed18b2c5707b6332ebe87b789fd768eb01b, 6.1.189; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 230234d12ce42ab04132a32c3a848f07a5d27a71, 3d42fed18b2c5707b6332ebe87b789fd768eb01b, 6.1.189; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 8d505d06d7330f5d67d3e5e9e1c647fb0b10ddad, 6.4affected
- 7403630eb94c1d664fb873f967427ef2f6ee3699 and later · before a2652fcf96b63e9da04951e4e58e6a0672df695daffected · git
- e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c and later · before 3d42fed18b2c5707b6332ebe87b789fd768eb01baffected · git
- e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c and later · before e787361bb6b0026ea3eb4d3fa7a304c7fcb99555affected · git
- e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c and later · before b22dc0add7d72b8bd9cae3188db0dd65da1c8652affected · git
- e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c and later · before 891c21f6d5673b2a519b536243bfc6dd2d35beb6affected · git
- e30fbc618e97b38dbb49f1d44dcd0778d3f23b8c and later · before 230234d12ce42ab04132a32c3a848f07a5d27a71affected · git
- 6.1.33 and later · before 6.1.189affected · semver
- 6.3.7 and later · before 6.4affected · semver
- before 6.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-97919Sep 25, 2026 · tracing: Take the reference before publishing the named histogram trigger0Monitor
- ← EarlierCVE-2026-97920Sep 25, 2026 · tracing: Keep the entry count when the histogram stats allocation fails0Monitor
- Later →CVE-2026-97922Sep 25, 2026 · tracing: Free histogram var refs regardless of how often they are referenced0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 230234d12ce42ab04132a32c3a848f07a5d27a71 | Vendor (CNA) |
| Linux Linux | 3d42fed18b2c5707b6332ebe87b789fd768eb01b | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| Linux Linux | 891c21f6d5673b2a519b536243bfc6dd2d35beb6 | Vendor (CNA) |
| Linux Linux | a2652fcf96b63e9da04951e4e58e6a0672df695d | Vendor (CNA) |
| Linux Linux | b22dc0add7d72b8bd9cae3188db0dd65da1c8652 | Vendor (CNA) |
| Linux Linux | e787361bb6b0026ea3eb4d3fa7a304c7fcb99555 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1184 · Sep 28, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3d42fed18b2c5707b6332ebe87b789fd768eb01b
- git.kernel.org/stable/c/891c21f6d5673b2a519b536243bfc6dd2d35beb6
- git.kernel.org/stable/c/a2652fcf96b63e9da04951e4e58e6a0672df695d
- git.kernel.org/stable/c/b22dc0add7d72b8bd9cae3188db0dd65da1c8652
- git.kernel.org/stable/c/e787361bb6b0026ea3eb4d3fa7a304c7fcb99555
Vendor advisories and official records. Exploit/PoC links are deliberately left out.