CVE-2026-63993

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu()

skb_tunnel_check_pmtu() can change skb->head.

Reusing old_iph afer skb_tunnel_check_pmtu() can cause an UAF.

Use instead ip_hdr(skb) as done in drivers/net/bareudp.c and drivers/net/geneve.c.

Found by Sashiko.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5303925e360527243b46a440a04667826bbc72b7
generic

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/609e63312c29aad18026a1d3222e123d4b6b0feb
generic

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9257f56ac47ef1976bcd056cf986a9988eeec67a
generic

vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b8bfce9d2f774d2c2243e0248e03efb99bba6c0

Vendor Advisories for CVE-2026-63993(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-63993?
CVE-2026-63993 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: vxlan: do not reuse cached iphdr() value after skbtunnelcheckpmtu() skbtunnelcheck_pmtu() can change skb->head. Reusing oldiph afer skbtunnelcheckpmtu() can cause an UAF. Use instead ip_hdr(skb) as done in drivers/net/bareudp.c and…
When was CVE-2026-63993 disclosed?
CVE-2026-63993 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63993 actively exploited?
CVE-2026-63993 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63993?
CVE-2026-63993 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63993?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63993, 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-63993

Explore →

Is Your Infrastructure Affected by CVE-2026-63993?

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

Start Free Scan →Browse All CVEs