CVE-2026-64576

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
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.1Exploit: 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:

nexthop: initialize extack in nh_res_bucket_migrate()

nh_res_bucket_migrate() passes an uninitialized netlink_ext_ack to call_nexthop_res_bucket_notifiers(). When nh_notifier_res_bucket_info_init() fails (e.g. the kzalloc returns -ENOMEM), the error is propagated back before any notifier sets extack._msg, and the error path formats the stale pointer with pr_err_ratelimited("%s\n", extack._msg). With CONFIG_INIT_STACK_NONE this dereferences uninitialized stack memory:

Oops: general protection fault, probably for non-canonical address ... KASAN: maybe wild-memory-access in range [...] RIP: 0010:string (lib/vsprintf.c:730) vsnprintf (lib/vsprintf.c:2945) _printk (kernel/printk/printk.c:2504) nh_res_bucket_migrate (net/ipv4/nexthop.c:1816) nh_res_table_upkeep (net/ipv4/nexthop.c:1866) rtm_new_nexthop (net/ipv4/nexthop.c:3323) rtnetlink_rcv_msg (net/core/rtnetlink.c:7076) netlink_sendmsg (net/netlink/af_netlink.c:1900) Kernel panic - not syncing: Fatal exception

Zero-initialize extack so _msg is NULL on error paths that never set it.

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

Published

August 5, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

nexthop: initialize extack in nh_res_bucket_migrate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nexthop: initialize extack in nh_res_bucket_migrate() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nexthop: initialize extack in nh_res_bucket_migrate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6347c5314cee49f364aaf2e40ff15415a57a116e
generic

nexthop: initialize extack in nh_res_bucket_migrate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3081702ea5aca0aeed9c1ade8eadf6cde8db6b7d
generic

nexthop: initialize extack in nh_res_bucket_migrate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18506d7263768d76ac8e057ba55a4d9da50aad66

Vendor Advisories for CVE-2026-64576(2)

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

Affected Packages

(3 across 3 ecosystems)
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 46× in last 7d / 80× 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 16:50 UTCVendor advisory
  2. 2026-08-20 16:50 UTCGHSA enrichment
  3. 2026-08-20 05:09 UTCGHSA enrichment
  4. 2026-08-19 17:27 UTCEG score recompute
  5. 2026-08-19 17:27 UTCVendor advisory
  6. 2026-08-19 17:27 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:56 UTCEG score recompute
  9. 2026-08-19 16:56 UTCVendor advisory
  10. 2026-08-19 16:56 UTCGHSA enrichment
  11. 2026-08-19 06:24 UTCVendor advisory
  12. 2026-08-19 06:24 UTCGHSA enrichment
  13. 2026-08-18 18:15 UTCVendor advisory
  14. 2026-08-18 18:15 UTCGHSA enrichment
  15. 2026-08-18 05:13 UTCGHSA enrichment
  16. 2026-08-17 17:29 UTCEG score recompute
  17. 2026-08-17 17:29 UTCVendor advisory
  18. 2026-08-17 17:29 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 05:42 UTCEG score recompute
  21. 2026-08-17 05:42 UTCVendor advisory
  22. 2026-08-17 05:42 UTCGHSA enrichment
  23. 2026-08-17 05:13 UTCEG score recompute
  24. 2026-08-17 05:13 UTCVendor advisory
  25. 2026-08-17 05:13 UTCGHSA enrichment
Show 55 more
  1. 2026-08-16 22:08 UTCEG score recompute
  2. 2026-08-16 22:08 UTCVendor advisory
  3. 2026-08-16 22:08 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 10:25 UTCEG score recompute
  6. 2026-08-16 10:25 UTCVendor advisory
  7. 2026-08-16 10:25 UTCGHSA enrichment
  8. 2026-08-15 22:44 UTCVendor advisory
  9. 2026-08-15 22:44 UTCGHSA enrichment
  10. 2026-08-15 11:02 UTCEG score recompute
  11. 2026-08-15 11:02 UTCVendor advisory
  12. 2026-08-15 11:02 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 23:19 UTCVendor advisory
  15. 2026-08-14 23:19 UTCGHSA enrichment
  16. 2026-08-14 11:37 UTCVendor advisory
  17. 2026-08-14 11:37 UTCGHSA enrichment
  18. 2026-08-13 23:56 UTCEG score recompute
  19. 2026-08-13 23:56 UTCVendor advisory
  20. 2026-08-13 23:56 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 12:14 UTCVendor advisory
  23. 2026-08-13 12:14 UTCGHSA enrichment
  24. 2026-08-13 00:32 UTCEG score recompute
  25. 2026-08-13 00:32 UTCGHSA enrichment
  26. 2026-08-12 13:51 UTCEPSS rescore
  27. 2026-08-12 12:51 UTCVendor advisory
  28. 2026-08-12 12:51 UTCGHSA enrichment
  29. 2026-08-12 01:09 UTCEG score recompute
  30. 2026-08-12 01:09 UTCVendor advisory
  31. 2026-08-12 01:09 UTCGHSA enrichment
  32. 2026-08-11 13:27 UTCVendor advisory
  33. 2026-08-11 13:27 UTCGHSA enrichment
  34. 2026-08-11 01:45 UTCEG score recompute
  35. 2026-08-11 01:45 UTCVendor advisory
  36. 2026-08-11 01:45 UTCGHSA enrichment
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 14:04 UTCVendor advisory
  39. 2026-08-10 14:04 UTCGHSA enrichment
  40. 2026-08-10 02:22 UTCGHSA enrichment
  41. 2026-08-09 14:40 UTCEG score recompute
  42. 2026-08-09 14:40 UTCGHSA enrichment
  43. 2026-08-09 13:47 UTCEPSS rescore
  44. 2026-08-09 02:59 UTCEG score recompute
  45. 2026-08-09 02:59 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 15:17 UTCEG score recompute▲ 7.10
  48. 2026-08-08 15:17 UTCGHSA enrichment
  49. 2026-08-08 15:16 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  50. 2026-08-06 13:47 UTCEPSS rescore
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-05 08:20 UTCNVD update
  54. 2026-08-05 08:12 UTCEG score recompute
  55. 2026-08-05 08:10 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64576?
CVE-2026-64576 is a high vulnerability published on August 5, 2026. In the Linux kernel, the following vulnerability has been resolved: nexthop: initialize extack in nhresbucket_migrate() nhresbucketmigrate() passes an uninitialized netlinkext_ack to callnexthopresbucketnotifiers(). When nhnotifierresbucketinfo_init() fails (e.g. the kzalloc returns -ENOMEM), the…
When was CVE-2026-64576 disclosed?
CVE-2026-64576 was first published in the National Vulnerability Database on August 5, 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-64576 actively exploited?
CVE-2026-64576 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64576?
CVE-2026-64576 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64576?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64576, 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-64576

Explore →

Is Your Infrastructure Affected by CVE-2026-64576?

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

Start Free Scan →Browse All CVEs