CVE-2026-63924

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:

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo()

ipv6_hop_jumbo() calls pskb_trim_rcsum(), which can change skb pointers. Let's recompute nh pointer to make sure any change won't mess things up.

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
51%
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

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b56bbd928c030894c270cd33d60286326919458
generic

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72af7beae774e46ed543f3f2f267bf0a141bfcdd
generic

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e883eaa878f4337b5873c706efb5a192364ed18
generic

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/645b99b1a185c91a79bdac4c5de0f91b212d64f0
generic

ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b3ac54e5c905f86d22b502eacb5686a282c5659f

Vendor Advisories for CVE-2026-63924(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-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
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-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 57× in last 7d / 341× 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 416 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63924?
CVE-2026-63924 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: exthdrs: refresh nh pointer after ipv6hopjumbo() ipv6hopjumbo() calls pskbtrimrcsum(), which can change skb pointers. Let's recompute nh pointer to make sure any change won't mess things up.
When was CVE-2026-63924 disclosed?
CVE-2026-63924 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-63924 actively exploited?
CVE-2026-63924 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 49.3% of all scored CVEs.
What is the CVSS score of CVE-2026-63924?
CVE-2026-63924 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63924?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63924, 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-63924

Explore →

Is Your Infrastructure Affected by CVE-2026-63924?

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

Start Free Scan →Browse All CVEs