CVE-2026-53006

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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:

ipv6: fix possible UAF in icmpv6_rcv()

Caching saddr and daddr before pskb_pull() is problematic since skb->head can change.

Remove these temporary variables:

  • We only access &ipv6_hdr(skb)->saddr and &ipv6_hdr(skb)->daddr
when net_dbg_ratelimited() is called in the slow path.
  • Avoid potential future misuse after pskb_pull() call.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
—
EPSS
31.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 16, 2026
Patch available. Sources: redhat.
redhat

2492363 – (CVE-2026-53006) CVE-2026-53006 kernel: ipv6: fix possible UAF in icmpv6_rcv()

https://bugzilla.redhat.com/show_bug.cgi?id=2492363
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-53006
generic

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c66b368c6ff453f99cb39d84af93e908e51eef2
generic

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bff2c8fe5c35ae58bf73104f53db3676e6e5d94
generic

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38bdbc897c0d83a3e2b925a51b69420f1feba29a
generic

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/085e31a811ef234ef8c3e219c4636dfebfe7e10f
generic

ipv6: fix possible UAF in icmpv6_rcv() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0069813e6ca9309eca78022bcb3aeb1e9ef90a12

Vendor Advisories for CVE-2026-53006(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-53006?
CVE-2026-53006 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible UAF in icmpv6_rcv() Caching saddr and daddr before pskb_pull() is problematic since skb->head can change. Remove these temporary variables: We only access &ipv6hdr(skb)->saddr and &ipv6hdr(skb)->daddr when…
When was CVE-2026-53006 disclosed?
CVE-2026-53006 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53006 actively exploited?
CVE-2026-53006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53006?
CVE-2026-53006 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53006, 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-53006

Explore →

Is Your Infrastructure Affected by CVE-2026-53006?

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

Start Free Scan →Browse All CVEs