CVE-2026-64163
Vulnérabilité non évaluée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: test_kprobes: clear kprobes between test runs Running the kprobes sanity tests twice makes all tests fail and eventually crashes the kernel. [root@martin-riscv-1 ~]# echo 1 > /sys/kernel/debug/kunit/kprobes_test/run ... # Totals: pass:5 fail:0 skip:0 total:5 ok 1 kprobes_test [root@martin-riscv-1 ~]# echo 1 > /sys/kernel/debug/kunit/kprobes_test/run ... # test_kprobe: EXPECTATION FAILED at lib/tests/test_kprobes.c:64 Expected 0 == register_kprobe(&kp), but register_kprobe(&kp) == -22 (0xffffffffffffffea) ... Unable to handle kernel paging request ... The testsuite defines several kprobes and kretprobes as static variables that are preserved across test runs. After register_kprobe and unregister_kprobe, a kprobe contains some leftover data that must be cleared before the kprobe can be registered again. The tests are setting symbol_name to define the probe location. Address and flags must be cleared. The existing code clears some of the probes between subsequent tests, but not between two test runs. The leftover data from a previous test run makes the registrations fail in the next run. Move the cleanups for all kprobes into kprobes_test_init, this function is called before each single test (including the first test of a test run).
Gravité et risque d'exploitation
CVE-2026-64163 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.12 %, ce qui la place devant 1.6 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <=7.0.*, <=6.12.*, 5.16, 0, e44e81c5b90f698025eadceb7eef8661eda117d5, <96515819d79f356f40da5540968d838ea570fab9, 6.12.92, 6.6.142, <=6.6.*, <accc0004c501a9918313142282b094d408af06fb, 6.18.34, <5.16, 7.1, <=6.18.*, 7.0.11, <1c24cf1fd67f6702c719ab73499392cb7af956ae, <=*, <ef5581bb30efb939cc2bf093475c6cc85258e5cd, <08d355936fcf70c81c94f9fe7310450b65c53399) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- https://git.kernel.org/stable/c/08d355936fcf70c81c94f9fe7310450b65c53399
- https://git.kernel.org/stable/c/accc0004c501a9918313142282b094d408af06fb
- https://git.kernel.org/stable/c/1c24cf1fd67f6702c719ab73499392cb7af956ae
- https://git.kernel.org/stable/c/96515819d79f356f40da5540968d838ea570fab9
- https://git.kernel.org/stable/c/ef5581bb30efb939cc2bf093475c6cc85258e5cd