CVE-2026-64550

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.3EG
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.3Exploit: 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: validate MAP frame length before ingress parsing

When ingress deaggregation is disabled, rmnet_map_ingress_handler() passes the skb straight to __rmnet_map_ingress_handler(), skipping the length validation that rmnet_map_deaggregate() performs on the aggregated path. The parser then dereferences the MAP header and csum header/trailer based on the on-wire pkt_len without checking skb->len, so a short frame is read out of bounds:

BUG: KASAN: slab-out-of-bounds in rmnet_map_checksum_downlink_packet Read of size 1 at addr ffff88801118ed00 by task exploit/147 Call Trace: ... rmnet_map_checksum_downlink_packet (drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c:413) __rmnet_map_ingress_handler (drivers/net/ethernet/qualcomm/rmnet/rmnet_handlers.c:96) rmnet_rx_handler (drivers/net/ethernet/qualcomm/rmnet/rmnet_handlers.c:129) __netif_receive_skb_core.constprop.0 (net/core/dev.c:6089) netif_receive_skb (net/core/dev.c:6460) tun_get_user (drivers/net/tun.c:1955) tun_chr_write_iter (drivers/net/tun.c:2001) vfs_write (fs/read_write.c:688) ksys_write (fs/read_write.c:740) do_syscall_64 (arch/x86/entry/syscall_64.c:94) ...

Factor that validation out of rmnet_map_deaggregate() into rmnet_map_validate_packet_len() and run it on the no-aggregation path too. The MAP header is bounds-checked first, since this path can receive a frame shorter than the header.

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

Published

July 27, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3868c3244369ab709a90c9aad7534d406009b824
generic

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/231a8a4b76cb1b1827b3b19d7b3603642f5aaaef
generic

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b12612c367e4be9b0814c0468e7e687835315b4
generic

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14eb0c9491385d5361a292ea4974aec0e6887299
generic

net: qualcomm: rmnet: validate MAP frame length before ingress parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00f4c366dbca16a40772c3b7ec2d8cba839e9724

Vendor Advisories for CVE-2026-64550(1)

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.12—6.12.100-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)7.1.5-1—

Data Freshness Timeline

(refreshed 19× in last 7d / 107× 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 122 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64550?
CVE-2026-64550 is a high vulnerability published on July 27, 2026. In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: validate MAP frame length before ingress parsing When ingress deaggregation is disabled, rmnetmapingress_handler() passes the skb straight to rmnetmapingress_handler(), skipping the length validation that…
When was CVE-2026-64550 disclosed?
CVE-2026-64550 was first published in the National Vulnerability Database on July 27, 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-64550 actively exploited?
CVE-2026-64550 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-64550?
CVE-2026-64550 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-64550?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64550, 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-64550

Explore →

Is Your Infrastructure Affected by CVE-2026-64550?

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

Start Free Scan →Browse All CVEs