Answer in brief
CVE-2026-64163 records a Medium severity (CVSS 5.5) vulnerability in test_kprobes: clear kprobes between test runs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e44e81c5b90f698025eadceb7eef8661eda117d5 <29ec976006dfab171a7e007976e38af56ce286e4 || >=e44e81c5b90f698025eadceb7eef8661eda117d5 <08d355936fcf70c81c94f9fe7310450b65c53399 || >=e44e81c5b90f698025eadceb7eef8661eda117d5 <accc0004c501a9918313142282b094d408af06fb || >=e44e81c5b90f698025eadceb7eef8661eda117d5 <1c24cf1fd67f6702c719ab73499392cb7af956ae || >=e44e81c5b90f698025eadceb7eef8661eda117d5 <96515819d79f356f40da5540968d838ea570fab9 || >=e44e81c5b90f698025eadceb7eef8661eda117d5 <ef5581bb30efb939cc2bf093475c6cc85258e5cd | 29ec976006dfab171a7e007976e38af56ce286e4, 08d355936fcf70c81c94f9fe7310450b65c53399, accc0004c501a9918313142282b094d408af06fb, 1c24cf1fd67f6702c719ab73499392cb7af956ae, 96515819d79f356f40da5540968d838ea570fab9, ef5581bb30efb939cc2bf093475c6cc85258e5cd |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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).
Quoted source text, attributed separately from HOL analysis.