CVE-2026-46037

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ipv4: icmp: validate reply type before using icmp_pointers

Extended echo replies use ICMP_EXT_ECHOREPLY as the outbound reply type. That value is outside the range covered by icmp_pointers[], which only describes the traditional ICMP types up to NR_ICMP_TYPES.

Avoid consulting icmp_pointers[] for reply types outside that range, and use array_index_nospec() for the remaining in-range lookup. Normal ICMP replies keep their existing behavior unchanged.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
35.4%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (7)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93df2af4f491de33827550b9d420f01808c0706b
generic

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92e7c209036dcc0e8ffdf806fdfd3645b263bea5
generic

ipv4: icmp: validate reply type before using icmp_pointers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67bf002a2d7387a6312138210d0bd06e3cf4879b

Patch Availability(5)

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.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-46037?
CVE-2026-46037 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv4: icmp: validate reply type before using icmp_pointers Extended echo replies use ICMPEXTECHOREPLY as the outbound reply type. That value is outside the range covered by icmp_pointers[], which only describes the traditional ICMP…
When was CVE-2026-46037 disclosed?
CVE-2026-46037 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46037 actively exploited?
CVE-2026-46037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46037?
CVE-2026-46037 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-46037?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46037, 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

Explore the affected products and dependency analysis for CVE-2026-46037

Explore →

Is Your Infrastructure Affected by CVE-2026-46037?

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