GHSA-R69X-P84R-2WC9
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In 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": [],
"aliases": [
"CVE-2026-97920"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:19Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Keep the entry count when the histogram stats allocation fails\n\nprint_entries() uses n_entries both as the number of sort entries and as\nits own return value, so the -ENOMEM it stores when the stats allocation\nfails overwrites the count that the cleanup still needs:\n\n\tn_entries = tracing_map_sort_entries(map, ...);\n\tif (n_entries \u003c 0)\n\t\treturn n_entries;\n\t...\n\t\t\tif (!stats) {\n\t\t\t\tn_entries = -ENOMEM;\n\t\t\t\tgoto out;\n\t\t\t}\n\t...\n out:\n\ttracing_map_destroy_sort_entries(sort_entries, n_entries);\n\ntracing_map_destroy_sort_entries() takes an unsigned int and loops up to\nit, so -ENOMEM arrives as 4294967284. It walks an array of at most\nmap-\u003emax_elts pointers and calls destroy_sort_entry(), which dereferences\nand frees, on whatever lies past the end.\n\nReading the hist file of a trigger with a .percent value, with that\nallocation forced to fail:\n\n BUG: KASAN: vmalloc-out-of-bounds in tracing_map_destroy_sort_entries+0xa0/0xb0\n Read of size 8 at addr ffffc90000045000 by task init/1\n tracing_map_destroy_sort_entries+0xa0/0xb0\n hist_show+0x6f7/0x1df0\n seq_read_iter+0x2b8/0x1190\n vfs_read+0x176/0xa40\n The buggy address belongs to a 4-page vmalloc region starting at\n ffffc90000041000 allocated at tracing_map_sort_entries+0x5c/0xd50\n\nA few pages further the fault is fatal. The registers at the oops confirm\nthe bound: the loop\u0027s end pointer less the array start, over the pointer\nsize, is 4294967284.\n\nReturn the error in a separate variable and leave n_entries holding the\ncount, the way tracing_map_sort_entries() does on its own error path.\n\nThe stats block is only entered for a value carrying .percent or .graph,\nwhich __create_val_field() has rejected since v6.3, so this cannot be\nreached in mainline as it stands. It becomes reachable again with\n\"tracing: hist: let values keep the percent and graph modifiers\", so it\nshould be applied first.",
"id": "GHSA-r69x-p84r-2wc9",
"modified": "2026-09-25T12:31:28Z",
"published": "2026-09-25T12:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97920"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/06f5634ec5584954177f9a22e36b3bfb398a971b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/17e87ce55f877efff1b08fe509e8bf91378cbbc9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9bd8321f5370295d1ae96dd17d43be3c9edd441b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c80b2a8067d58ff7d268ceef781c68b37a16c321"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.