CVE-2026-64163

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> test_kprobes: clear kprobes between test runs<br /> <br /> Running the kprobes sanity tests twice makes all tests fail and<br /> eventually crashes the kernel.<br /> <br /> [root@martin-riscv-1 ~]# echo 1 &gt; /sys/kernel/debug/kunit/kprobes_test/run<br /> ...<br /> # Totals: pass:5 fail:0 skip:0 total:5<br /> ok 1 kprobes_test<br /> [root@martin-riscv-1 ~]# echo 1 &gt; /sys/kernel/debug/kunit/kprobes_test/run<br /> ...<br /> # test_kprobe: EXPECTATION FAILED at lib/tests/test_kprobes.c:64<br /> Expected 0 == register_kprobe(&amp;kp), but<br /> register_kprobe(&amp;kp) == -22 (0xffffffffffffffea)<br /> ...<br /> Unable to handle kernel paging request ...<br /> <br /> The testsuite defines several kprobes and kretprobes as static variables<br /> that are preserved across test runs.<br /> <br /> After register_kprobe and unregister_kprobe, a kprobe contains some<br /> leftover data that must be cleared before the kprobe can be registered<br /> again. The tests are setting symbol_name to define the probe location.<br /> Address and flags must be cleared.<br /> <br /> The existing code clears some of the probes between subsequent tests, but<br /> not between two test runs. The leftover data from a previous test run<br /> makes the registrations fail in the next run.<br /> <br /> Move the cleanups for all kprobes into kprobes_test_init, this function<br /> is called before each single test (including the first test of a test<br /> run).