CVE-2026-64563

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — 4 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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

August 19, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
Patch available.
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(6)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-687.46.1.el9_82026-09-10redhat
redhatkernel-0:4.18.0-553.160.1.el8_102026-09-09redhat
redhatkernel-0:6.12.0-211.52.1.el10_22026-09-08redhat
redhatkernel-rt-0:4.18.0-553.160.1.rt7.501.el8_102026-09-08redhat

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

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1
  • every version up to 6.12.101-1~deb12u1: fixed in 6.12.101-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)
  • every version up to 6.12.101-1: fixed in 6.12.101-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (161 versions)
  • every version up to 7.1.6-1: fixed in 7.1.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 112× 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 224 total refreshes for this CVE.

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

Related CVEs(same vendor)

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 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.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64563?
CVE-2026-64563 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64563?
A fix for CVE-2026-64563 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64563 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs