CVE-2026-64163

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

test_kprobes: clear kprobes between test runs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef5581bb30efb939cc2bf093475c6cc85258e5cd
generic

test_kprobes: clear kprobes between test runs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/accc0004c501a9918313142282b094d408af06fb
generic

test_kprobes: clear kprobes between test runs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96515819d79f356f40da5540968d838ea570fab9
generic

test_kprobes: clear kprobes between test runs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c24cf1fd67f6702c719ab73499392cb7af956ae
generic

test_kprobes: clear kprobes between test runs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08d355936fcf70c81c94f9fe7310450b65c53399

Vendor Advisories for CVE-2026-64163(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 21× in last 7d / 83× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 113 total refreshes for this CVE.

  1. 2026-08-30 02:44 UTCEG score recompute
  2. 2026-08-30 02:44 UTCVendor advisory
  3. 2026-08-30 02:44 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:21 UTCEG score recompute
  7. 2026-08-27 21:21 UTCVendor advisory
  8. 2026-08-27 21:21 UTCGHSA enrichment
  9. 2026-08-26 22:13 UTCEG score recompute
  10. 2026-08-26 22:13 UTCVendor advisory
  11. 2026-08-26 22:13 UTCGHSA enrichment
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 22:43 UTCEG score recompute
  14. 2026-08-25 22:43 UTCVendor advisory
  15. 2026-08-25 22:43 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 23:19 UTCEG score recompute
  18. 2026-08-24 23:19 UTCVendor advisory
  19. 2026-08-24 23:19 UTCGHSA enrichment
  20. 2026-08-24 00:45 UTCVendor advisory
  21. 2026-08-24 00:45 UTCGHSA enrichment
  22. 2026-08-23 02:12 UTCEG score recompute
  23. 2026-08-23 02:12 UTCVendor advisory
  24. 2026-08-23 02:12 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-22 03:38 UTCEG score recompute
  2. 2026-08-22 03:38 UTCVendor advisory
  3. 2026-08-22 03:38 UTCGHSA enrichment
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 05:04 UTCEG score recompute
  6. 2026-08-21 05:04 UTCVendor advisory
  7. 2026-08-21 05:04 UTCGHSA enrichment
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 06:30 UTCEG score recompute
  10. 2026-08-20 06:30 UTCVendor advisory
  11. 2026-08-20 06:30 UTCGHSA enrichment
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 07:56 UTCEG score recompute
  14. 2026-08-19 07:56 UTCVendor advisory
  15. 2026-08-19 07:56 UTCGHSA enrichment
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-18 09:23 UTCEG score recompute
  18. 2026-08-18 09:23 UTCVendor advisory
  19. 2026-08-18 09:22 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 09:54 UTCEG score recompute
  22. 2026-08-17 09:54 UTCVendor advisory
  23. 2026-08-17 09:54 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:20 UTCEG score recompute
  26. 2026-08-16 11:20 UTCVendor advisory
  27. 2026-08-16 11:20 UTCGHSA enrichment
  28. 2026-08-15 12:47 UTCEG score recompute
  29. 2026-08-15 12:47 UTCVendor advisory
  30. 2026-08-15 12:47 UTCGHSA enrichment
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 14:10 UTCEG score recompute
  33. 2026-08-14 14:10 UTCVendor advisory
  34. 2026-08-14 14:10 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 15:36 UTCEG score recompute▲ 5.50
  37. 2026-08-13 15:36 UTCVendor advisory
  38. 2026-08-13 15:36 UTCGHSA enrichment
  39. 2026-08-13 15:36 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-10 20:41 UTCVendor advisory
  43. 2026-08-10 20:41 UTCGHSA enrichment
  44. 2026-08-09 13:47 UTCEPSS rescore
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 01:22 UTCVendor advisory
  47. 2026-08-08 01:22 UTCGHSA enrichment
  48. 2026-08-06 13:47 UTCEPSS rescore
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-05 06:02 UTCGHSA enrichment
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:39 UTCEPSS rescore
  54. 2026-08-03 10:36 UTCEPSS rescore
  55. 2026-08-02 10:39 UTCVendor advisory
  56. 2026-08-02 10:39 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 04:16 UTCEPSS rescore
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 15:19 UTCEG score recompute
  61. 2026-07-30 15:19 UTCGHSA enrichment
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-29 06:11 UTCGHSA enrichment
  65. 2026-07-28 15:37 UTCEPSS rescore
  66. 2026-07-27 14:14 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 10:51 UTCEG score recompute
  70. 2026-07-26 10:51 UTCVendor advisory
  71. 2026-07-26 10:51 UTCGHSA enrichment
  72. 2026-07-25 14:18 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-24 14:18 UTCEPSS rescore
  75. 2026-07-24 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-64163?
CVE-2026-64163 is a medium vulnerability published on July 19, 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:…
When was CVE-2026-64163 disclosed?
CVE-2026-64163 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64163 actively exploited?
CVE-2026-64163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64163?
CVE-2026-64163 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64163, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64163

Explore →

Is Your Infrastructure Affected by CVE-2026-64163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs