CVE-2026-64423

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. 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%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:

ipv4: igmp: remove multicast group from hash table on device destruction

When a device is destroyed under RTNL, ip_mc_destroy_dev() iterates through the multicast list and calls ip_ma_put() on each membership, scheduling them for RCU reclamation. However, they are not unlinked from the device's multicast hash table (mc_hash).

Since the device remains published in dev->ip_ptr until after ip_mc_destroy_dev() completes, concurrent RCU readers traversing mc_hash can still locate and access the multicast group after its refcount is decremented. If the RCU callback runs and frees the group while a reader is accessing it, a use-after-free occurs.

Fix this by unlinking the multicast group from mc_hash using ip_mc_hash_remove() before scheduling it for reclamation.

BUG: KASAN: slab-use-after-free in ip_check_mc_rcu+0x149/0x3f0 Read of size 4 at addr ffff888009bf1408 by task mausezahn/2276

Call Trace: dump_stack_lvl+0x67/0x90 print_report+0x175/0x7c0 kasan_report+0x147/0x180 ip_check_mc_rcu+0x149/0x3f0 udp_v4_early_demux+0x36d/0x12d0 ip_rcv_finish_core+0xb8b/0x1390 ip_rcv_finish+0x54/0x120 NF_HOOK+0x213/0x2b0 __netif_receive_skb+0x126/0x340 process_backlog+0x4f2/0xf00 __napi_poll+0x92/0x2c0 net_rx_action+0x583/0xc60 handle_softirqs+0x236/0x7f0 do_softirq+0x57/0x80

Allocated by task 2239: kasan_save_track+0x3e/0x80 __kasan_kmalloc+0x72/0x90 ____ip_mc_inc_group+0x31a/0xa40 __ip_mc_join_group+0x334/0x3f0 do_ip_setsockopt+0x16fa/0x2010 ip_setsockopt+0x3f/0x90 do_sock_setsockopt+0x1ad/0x300

Freed by task 0: kasan_save_track+0x3e/0x80 kasan_save_free_info+0x40/0x50 __kasan_slab_free+0x3a/0x60 __rcu_free_sheaf_prepare+0xd4/0x220 rcu_free_sheaf+0x36/0x190 rcu_core+0x8d9/0x12f0 handle_softirqs+0x236/0x7f0

CVSS v3
7.8
EG Score
7.8(medium)
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
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8820b530cb2388503d7418228d03ba074bf7a03e
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7993211bde166471dffac074dc965489f86531f8
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/76d030ac95e17f91d69a595f17ebc5979700cf9a
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f42729d74bd6c61306d864423290d92962de4e1
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/412ba7def06ffe974ba9a1d862b022362c54ffa5
generic

ipv4: igmp: remove multicast group from hash table on device destruction - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ca18df1c2611f70eb3eb487e02ae85eb703b284

Vendor Advisories for CVE-2026-64423(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 33× in last 7d / 149× 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 179 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64423?
CVE-2026-64423 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: remove multicast group from hash table on device destruction When a device is destroyed under RTNL, ipmcdestroy_dev() iterates through the multicast list and calls ipmaput() on each membership, scheduling them for RCU…
When was CVE-2026-64423 disclosed?
CVE-2026-64423 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64423 actively exploited?
CVE-2026-64423 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64423?
CVE-2026-64423 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64423?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64423, 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-64423

Explore →

Is Your Infrastructure Affected by CVE-2026-64423?

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