CVE-2026-64188

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink()

rmnet_dellink() removes the endpoint from the hash table with hlist_del_init_rcu() and then immediately frees it with kfree(). However, RCU readers on the receive path (rmnet_rx_handler -> __rmnet_map_ingress_handler) may still hold a reference to the endpoint and dereference ep->egress_dev after the memory has been freed. The endpoint is a kmalloc-32 object, and the stale read at offset 8 corresponds to the egress_dev pointer.

BUG: unable to handle page fault for address: ffffffffde942eef Oops: 0002 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 137 Comm: poc_write Not tainted 7.0.0+ #4 PREEMPTLAZY RIP: 0010:rmnet_vnd_rx_fixup (rmnet_vnd.c:27) Call Trace: __rmnet_map_ingress_handler (rmnet_handlers.c:48 rmnet_handlers.c:101) rmnet_rx_handler (rmnet_handlers.c:129 rmnet_handlers.c:235) __netif_receive_skb_core.constprop.0 (net/core/dev.c:6096) __netif_receive_skb_one_core (net/core/dev.c:6208) netif_receive_skb (net/core/dev.c:6467) tun_get_user (drivers/net/tun.c:1955) tun_chr_write_iter (drivers/net/tun.c:2003) vfs_write (fs/read_write.c:688) ksys_write (fs/read_write.c:740)

Add an rcu_head field to struct rmnet_endpoint and replace kfree() with kfree_rcu() so the endpoint memory remains valid through the RCU grace period. Also remove the rmnet_vnd_dellink() call and inline only the nr_rmnet_devs decrement, since rmnet_vnd_dellink() would set ep->egress_dev to NULL during the grace period, creating a data race with lockless readers.

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
2%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 11, 2026

Advisory Details (8)

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

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9918698cf3aee4032e12bb42fd5a951dc465339b
generic

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b17adf6d4fb6bf61fa4c3f58366a7c082799a71
generic

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41e06fcc5df0774d212e70c5b503fc769492bce3
generic

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/310b93246bfec7d4452507e0c15477377ed9f025
generic

net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1078ae8175777e80c9637996fb4a46c55f0ce576

Vendor Advisories for CVE-2026-64188(2)

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

Affected Packages

(5 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.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (143 versions)7.0.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 32× in last 7d / 136× 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 311 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64188?
CVE-2026-64188 is a high vulnerability published on July 20, 2026. In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: fix endpoint use-after-free in rmnet_dellink() rmnet_dellink() removes the endpoint from the hash table with hlistdelinit_rcu() and then immediately frees it with kfree(). However, RCU readers on the receive…
When was CVE-2026-64188 disclosed?
CVE-2026-64188 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64188 actively exploited?
CVE-2026-64188 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-64188?
CVE-2026-64188 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64188?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64188, 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-64188

Explore →

Is Your Infrastructure Affected by CVE-2026-64188?

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

Start Free Scan →Browse All CVEs