tracing: Keep the entry count when the histogram stats allocation fails
Summary
| CVE | CVE-2026-97920 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:19 UTC |
| Updated | 2026-10-19 10:17:42 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the entry count when the histogram stats allocation fails print_entries() uses n_entries both as the number of sort entries and as its own return value, so the -ENOMEM it stores when the stats allocation fails overwrites the count that the cleanup still needs: n_entries = tracing_map_sort_entries(map, ...); if (n_entries < 0) return n_entries; ... if (!stats) { n_entries = -ENOMEM; goto out; } ... out: tracing_map_destroy_sort_entries(sort_entries, n_entries); tracing_map_destroy_sort_entries() takes an unsigned int and loops up to it, so -ENOMEM arrives as 4294967284. It walks an array of at most map->max_elts pointers and calls destroy_sort_entry(), which dereferences and frees, on whatever lies past the end. Reading the hist file of a trigger with a .percent value, with that allocation forced to fail: BUG: KASAN: vmalloc-out-of-bounds in tracing_map_destroy_sort_entries+0xa0/0xb0 Read of size 8 at addr ffffc90000045000 by task init/1 tracing_map_destroy_sort_entries+0xa0/0xb0 hist_show+0x6f7/0x1df0 seq_read_iter+0x2b8/0x1190 vfs_read+0x176/0xa40 The buggy address belongs to a 4-page vmalloc region starting at ffffc90000041000 allocated at tracing_map_sort_entries+0x5c/0xd50 A few pages further the fault is fatal. The registers at the oops confirm the bound: the loop's end pointer less the array start, over the pointer size, is 4294967284. Return the error in a separate variable and leave n_entries holding the count, the way tracing_map_sort_entries() does on its own error path. The stats block is only entered for a value carrying .percent or .graph, which __create_val_field() has rejected since v6.3, so this cannot be reached in mainline as it stands. It becomes reachable again with "tracing: hist: let values keep the percent and graph modifiers", so it should be applied first. |
Risk And Classification
EPSS: 0.002050000 probability, percentile 0.095660000 (date 2026-10-05)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 93454d1a306ea975294b861d32ffa1e44b20c733 89c978d67ad01ce28223944cc58e95feea177b35 git | Not specified |
| CNA | Linux | Linux | affected abaa5258ce5e5887a9de049f50a85dc023391a1c fe05eeed27128e17d38dbc0af02e4470bcecda89 git | Not specified |
| CNA | Linux | Linux | affected abaa5258ce5e5887a9de049f50a85dc023391a1c 9bd8321f5370295d1ae96dd17d43be3c9edd441b git | Not specified |
| CNA | Linux | Linux | affected abaa5258ce5e5887a9de049f50a85dc023391a1c c80b2a8067d58ff7d268ceef781c68b37a16c321 git | Not specified |
| CNA | Linux | Linux | affected abaa5258ce5e5887a9de049f50a85dc023391a1c 17e87ce55f877efff1b08fe509e8bf91378cbbc9 git | Not specified |
| CNA | Linux | Linux | affected abaa5258ce5e5887a9de049f50a85dc023391a1c 06f5634ec5584954177f9a22e36b3bfb398a971b git | Not specified |
| CNA | Linux | Linux | affected 6.1.23 6.1.189 semver | Not specified |
| CNA | Linux | Linux | affected 6.2 | Not specified |
| CNA | Linux | Linux | unaffected 6.2 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.189 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.158 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.111 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/89c978d67ad01ce28223944cc58e95feea177b35 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/17e87ce55f877efff1b08fe509e8bf91378cbbc9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/fe05eeed27128e17d38dbc0af02e4470bcecda89 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9bd8321f5370295d1ae96dd17d43be3c9edd441b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/06f5634ec5584954177f9a22e36b3bfb398a971b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c80b2a8067d58ff7d268ceef781c68b37a16c321 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.