CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust

Published Aug 10, 2026
·
Updated

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

ila: reload IPv6 header after pskbmaypull in checksum adjust

ilacsumadjusttransport() caches ip6h = ipv6hdr(skb) before calling pskbmaypull(). On a non-linear skb whose transport header sits in a page fragment, pskbmaypull() can call pskbpulltail() / pskbexpandhead() and free the old skb head, leaving ip6h dangling; the following getcsumdiff(ip6h, p) then reads freed memory. ilaupdateipv6locator() uses ip6h (and the iaddr derived from it) again after the csum-adjust call and additionally writes the new locator through that pointer.

Impact: a remote IPv6 packet routed through a configured ILA csum-adjust-transport route or receive-side mapping triggers a slab-use-after-free in ilaupdateipv6locator() (KASAN). The route or mapping requires CAPNETADMIN to configure, but trigger packets are unauthenticated once it exists.

Reload ip6h after each pskbmaypull() in ilacsumadjusttransport() before the csum-diff read. In ilaupdateipv6locator() only the ILACSUMADJUSTTRANSPORT case pulls the skb, so reload ip6h and iaddr in that case alone before the destination-address write; the neutral-map modes never pull and keep their cached pointers.

Affected Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In ila_csum_adjust_transport(), do not reuse cached pointers to ip6h after pskb_may_pull(); reload the IPv6 header (ip6h) after each pskb_may_pull() before continuing with csum-diff reads and locator updates.

    Linux kernel (ILA) reload ip6h after pskb_may_pull() in ila_csum_adjust_transport() = implemented

Event History

Aug 10, 2026
CVE Published
via MITRE·11:58 AM
Data Sourced
via MITRE·11:58 AM
Description
Data Sourced
via NVD·01:19 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68127?

CVE-2026-68127 has a risk rating of 48.

2

How do I fix CVE-2026-68127?

To mitigate CVE-2026-68127, upgrade to the latest version of the Linux kernel where the vulnerability has been patched.

3

What type of vulnerability is CVE-2026-68127?

CVE-2026-68127 is categorized as a Use After Free vulnerability in the Linux kernel.

4

What does CVE-2026-68127 affect?

CVE-2026-68127 affects the IPv6 header processing in the Linux kernel.

5

When was CVE-2026-68127 published?

CVE-2026-68127 was published on August 10, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203