test_kprobes: clear kprobes between test runs
Summary
| CVE | CVE-2026-64163 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-07-19 16:17:58 UTC |
|---|
| Updated | 2026-07-19 16:17:58 UTC |
|---|
| 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). |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected e44e81c5b90f698025eadceb7eef8661eda117d5 08d355936fcf70c81c94f9fe7310450b65c53399 git |
Not specified |
| CNA |
Linux |
Linux |
affected e44e81c5b90f698025eadceb7eef8661eda117d5 accc0004c501a9918313142282b094d408af06fb git |
Not specified |
| CNA |
Linux |
Linux |
affected e44e81c5b90f698025eadceb7eef8661eda117d5 1c24cf1fd67f6702c719ab73499392cb7af956ae git |
Not specified |
| CNA |
Linux |
Linux |
affected e44e81c5b90f698025eadceb7eef8661eda117d5 96515819d79f356f40da5540968d838ea570fab9 git |
Not specified |
| CNA |
Linux |
Linux |
affected e44e81c5b90f698025eadceb7eef8661eda117d5 ef5581bb30efb939cc2bf093475c6cc85258e5cd git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.16 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.142 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.92 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.34 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.11 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/96515819d79f356f40da5540968d838ea570fab9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ef5581bb30efb939cc2bf093475c6cc85258e5cd |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1c24cf1fd67f6702c719ab73499392cb7af956ae |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/08d355936fcf70c81c94f9fe7310450b65c53399 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/accc0004c501a9918313142282b094d408af06fb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.
