CVE-2026-63924: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo()
In the Linux kernel, the following vulnerability has been resolved:
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.187-1Fixed in 6.12.107-1Fixed in 6.12.111-1Fixed in 7.2.8-1Fixed in 7.2.9-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.10.259 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.210 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.176 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.143 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.93 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.35 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.0.12
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63924?
CVE-2026-63924 has a critical severity rating of 9.8.
What is CVE-2026-63924 about?
CVE-2026-63924 is a vulnerability in the Linux kernel related to incorrect handling of the next header pointer during the ipv6_hop_jumbo() function.
How do I fix CVE-2026-63924?
To fix CVE-2026-63924, you should update to the latest patched version of the Linux kernel.
What systems are affected by CVE-2026-63924?
CVE-2026-63924 affects systems running vulnerable versions of the Linux kernel with IPv6 support.
Is there a workaround for CVE-2026-63924?
Currently, there are no known workarounds for CVE-2026-63924; applying the patch is the recommended method of mitigation.