Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64163test_kprobes: clear kprobes between test runs

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64163, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < 29ec976006dfab171a7e007976e38af56ce286e4
    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < 08d355936fcf70c81c94f9fe7310450b65c53399
    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < accc0004c501a9918313142282b094d408af06fb
    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < 1c24cf1fd67f6702c719ab73499392cb7af956ae
    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < 96515819d79f356f40da5540968d838ea570fab9
    • affected e44e81c5b90f698025eadceb7eef8661eda117d5 – < ef5581bb30efb939cc2bf093475c6cc85258e5cd
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64163 badge
[![CVE-2026-64163](https://cveledger.app/badge/CVE-2026-64163.svg)](https://cveledger.app/cve/CVE-2026-64163)

Record last updated .