CVSS
Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)
Атакува се
Време до експлоатация
Описание
Оригинално описание
In the Linux kernel, the following vulnerability has been resolved: tracing: Set the trace clock before registering the histogram trigger hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock: if (data->cmd_ops->init) { ret = data->cmd_ops->init(data); if (ret < 0) goto out; } if (hist_data->enable_timestamps) { ret = tracing_set_clock(file->tr, hist_data->attrs->clock); if (ret) { hist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); goto out; } The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object: ~# cd /sys/kernel/tracing/events/sched/sched_switch ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger bash: echo: write error: Invalid argument ~# echo 'hist:name=foo:keys=common_pid' > trigger BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0 Read of size 8 at addr ffff88800915d760 by task init/1 find_named_trigger+0xac/0xc0 hist_register_trigger+0xc1/0x900 event_hist_trigger_parse+0x3146/0x6af0 event_trigger_write+0xce/0x160 Freed by task 63: kfree+0x154/0x420 trigger_kthread_fn+0xfd/0x160 Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 ("tracing: Fix bad hist from corrupting named_triggers list") moved the registration below the rest of the setup. tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.
Засегнати продукти
- Linux Linux: a4072fe85ba3671720cab0788291af953db27318 преди 85e6df6e9cd489de8e238596a68b89eee0c03b88; a4072fe85ba3671720cab0788291af953db27318 преди 3568dabef3fb56517777ab981584f72ab1e90186; a4072fe85ba3671720cab0788291af953db27318 преди c7b77c22adcf314ec8aa4807f01914dcbc62ed54; a4072fe85ba3671720cab0788291af953db27318 преди 578d39ab420b18b76a12fc8d0573ec041a84da28; a4072fe85ba3671720cab0788291af953db27318 преди cc6c4cf565b0c187c61ffd2e67a4dfb2427675ad; a4072fe85ba3671720cab0788291af953db27318 преди cfad128171f8e2237a3c723d6478ef2cfb3b9127; a4072fe85ba3671720cab0788291af953db27318 преди 65d1e28198f344832a8a63e8ccf84b8f65b92a32; a4072fe85ba3671720cab0788291af953db27318 преди 6ede78d0563a2a3ae3e46f9c07cedb5d79645429
- Linux Linux: 4.17; преди 4.17; 5.10.273 до 5.10.*; 5.15.224 до 5.15.*; 6.1.191 до 6.1.*; 6.6.160 до 6.6.*; 6.12.112 до 6.12.*; 6.18.53 до 6.18.*; 7.2.7 до 7.2.*; от 7.3 нататък
История
- 25 септември 2026 Публикувано
Други уязвимости в Linux Linux
Първоизточници
- https://www.cve.org/CVERecord?id=CVE-2026-97935
- https://nvd.nist.gov/vuln/detail/CVE-2026-97935
- https://git.kernel.org/stable/c/85e6df6e9cd489de8e238596a68b89eee0c03b88
- https://git.kernel.org/stable/c/3568dabef3fb56517777ab981584f72ab1e90186
- https://git.kernel.org/stable/c/c7b77c22adcf314ec8aa4807f01914dcbc62ed54
- https://git.kernel.org/stable/c/578d39ab420b18b76a12fc8d0573ec041a84da28
- https://git.kernel.org/stable/c/cc6c4cf565b0c187c61ffd2e67a4dfb2427675ad
- https://git.kernel.org/stable/c/cfad128171f8e2237a3c723d6478ef2cfb3b9127
- https://git.kernel.org/stable/c/65d1e28198f344832a8a63e8ccf84b8f65b92a32
- https://git.kernel.org/stable/c/6ede78d0563a2a3ae3e46f9c07cedb5d79645429