CVE-2026-97920

published 25 Sep 2026 · updated 17 Nov 2026

tracing: Keep the entry count when the histogram stats allocation fails

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fe05eeed27128e17d38dbc0af02e4470bcecda89, Kernel 89c978d67ad01ce28223944cc58e95feea177b35, Kernel 06f5634ec5584954177f9a22e36b3bfb398a971b and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=abaa5258ce5e5887a9de049f50a85dc023391a1c <fe05eeed27128e17d38dbc0af02e4470bcecda89, >=93454d1a306ea975294b861d32ffa1e44b20c733 <89c978d67ad01ce28223944cc58e95feea177b35, >=abaa5258ce5e5887a9de049f50a85dc023391a1c <06f5634ec5584954177f9a22e36b3bfb398a971b, >=abaa5258ce5e5887a9de049f50a85dc023391a1c <17e87ce55f877efff1b08fe509e8bf91378cbbc9, >=abaa5258ce5e5887a9de049f50a85dc023391a1c <9bd8321f5370295d1ae96dd17d43be3c9edd441b, >=abaa5258ce5e5887a9de049f50a85dc023391a1c <c80b2a8067d58ff7d268ceef781c68b37a16c321, =6.2, >=6.1.23 <6.1.189fe05eeed27128e17d38dbc0af02e4470bcecda89, 89c978d67ad01ce28223944cc58e95feea177b35, 06f5634ec5584954177f9a22e36b3bfb398a971b, 17e87ce55f877efff1b08fe509e8bf91378cbbc9, 9bd8321f5370295d1ae96dd17d43be3c9edd441b, c80b2a8067d58ff7d268ceef781c68b37a16c321, 6.1.189
linux-kernel: Kernel>=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.158, >=6.7.0 <6.12.111, >=6.1.23 <6.1.1896.18.53, 7.2.7, 6.6.158, 6.12.111, 6.1.189

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97920 severity on Zeptric[![CVE-2026-97920](https://zeptric.io/badge/cve/CVE-2026-97920.svg)](https://zeptric.io/cve/CVE-2026-97920)