CVE-2026-64563

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

rhashtable: clear stale iter->p on table restart

rhashtable_walk_start_check() has two restart paths when resuming a walk. When iter->walker.tbl is valid, it re-validates iter->p against the table and sets iter->p = NULL if the object is gone. When iter->walker.tbl is NULL (table was freed during resize), it resets slot and skip but forgets to clear iter->p.

rhashtable_walk_next() then dereferences the stale iter->p, reading freed memory. This is a use-after-free.

Any caller that does multi-fragment rhashtable walks across walk_stop/walk_start boundaries is affected. Concrete cases include netlink_diag (__netlink_diag_dump in net/netlink/diag.c) and TIPC (tipc_nl_sk_walk in net/tipc/socket.c).

Crash stack (netlink_diag): BUG: KASAN: slab-use-after-free in rhashtable_walk_next+0x365/0x3c0 Read of size 8 at addr ffff88801a9d2438 (freed kmalloc-2k, offset 1080) Call Trace: rhashtable_walk_next+0x365/0x3c0 (lib/rhashtable.c:1016) __netlink_diag_dump+0x160/0x760 (net/netlink/diag.c:122) netlink_diag_dump+0xc2/0x240 netlink_dump+0x5bc/0x1270 netlink_recvmsg+0x7a3/0x980 sock_recvmsg+0x1bc/0x200 __sys_recvfrom+0x1d4/0x2c0

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 19, 2026

Advisory Details (3)

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

rhashtable: clear stale iter->p on table restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8173f7e2ce67e6ca1d4763f3da14e5b01ce77456
generic

rhashtable: clear stale iter->p on table restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4169d9fb92f313ff8e7e83d733c1ecdcc93eebd3
generic

rhashtable: clear stale iter->p on table restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ff7c1dbf722cf3fa538672452ba182318e0fcc3

Vendor Advisories for CVE-2026-64563(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.6-1—

Data Freshness Timeline

(refreshed 30× in last 7d / 67× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:32 UTCGHSA enrichment
  3. 2026-08-20 06:30 UTCGHSA enrichment
  4. 2026-08-19 17:27 UTCEG score recompute
  5. 2026-08-19 17:27 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:56 UTCEG score recompute
  8. 2026-08-19 16:56 UTCGHSA enrichment
  9. 2026-08-19 10:46 UTCGHSA enrichment
  10. 2026-08-18 21:43 UTCEG score recompute
  11. 2026-08-18 21:43 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 08:40 UTCGHSA enrichment
  14. 2026-08-17 19:35 UTCEG score recompute
  15. 2026-08-17 19:35 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:42 UTCEG score recompute
  18. 2026-08-17 05:42 UTCGHSA enrichment
  19. 2026-08-17 05:14 UTCEG score recompute
  20. 2026-08-17 05:14 UTCGHSA enrichment
  21. 2026-08-16 20:47 UTCEG score recompute
  22. 2026-08-16 20:47 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 07:44 UTCEG score recompute
  25. 2026-08-16 07:44 UTCGHSA enrichment
Show 42 more
  1. 2026-08-15 18:43 UTCGHSA enrichment
  2. 2026-08-15 05:41 UTCEG score recompute
  3. 2026-08-15 05:41 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 16:38 UTCGHSA enrichment
  6. 2026-08-14 03:36 UTCEG score recompute
  7. 2026-08-14 03:36 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 14:34 UTCGHSA enrichment
  10. 2026-08-13 01:32 UTCEG score recompute
  11. 2026-08-13 01:32 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 12:30 UTCGHSA enrichment
  14. 2026-08-11 23:28 UTCEG score recompute
  15. 2026-08-11 23:28 UTCGHSA enrichment
  16. 2026-08-11 10:26 UTCEG score recompute
  17. 2026-08-11 10:26 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 21:24 UTCGHSA enrichment
  20. 2026-08-10 08:21 UTCGHSA enrichment
  21. 2026-08-09 19:20 UTCEG score recompute
  22. 2026-08-09 19:20 UTCGHSA enrichment
  23. 2026-08-09 18:41 UTCEG score recompute
  24. 2026-08-09 18:41 UTCGHSA enrichment
  25. 2026-08-09 17:21 UTCEG score recompute
  26. 2026-08-09 17:21 UTCGHSA enrichment
  27. 2026-08-09 13:47 UTCEPSS rescore
  28. 2026-08-09 04:19 UTCEG score recompute
  29. 2026-08-09 04:19 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 15:17 UTCEG score recompute▲ 7.80
  32. 2026-08-08 15:17 UTCGHSA enrichment
  33. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  34. 2026-08-07 04:30 UTCEG score recompute
  35. 2026-08-07 04:30 UTCGHSA enrichment
  36. 2026-08-06 13:47 UTCEPSS rescore
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 07:17 UTCNVD update
  41. 2026-08-04 06:35 UTCEG score recompute
  42. 2026-08-04 06:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64563?
CVE-2026-64563 is a high vulnerability published on August 4, 2026. In the Linux kernel, the following vulnerability has been resolved: rhashtable: clear stale iter->p on table restart rhashtablewalkstart_check() has two restart paths when resuming a walk. When iter->walker.tbl is valid, it re-validates iter->p against the table and sets iter->p = NULL if the…
When was CVE-2026-64563 disclosed?
CVE-2026-64563 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64563 actively exploited?
CVE-2026-64563 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-64563?
CVE-2026-64563 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64563, 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-64563

Explore →

Is Your Infrastructure Affected by CVE-2026-64563?

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

Start Free Scan →Browse All CVEs