Skip to main content
VulnerabilityPublished Updated

CVE-2026-68127: Linux kernel · Use After Free

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in e451a904606c571f731ef7a06b3398619dce5300 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in e451a904606c571f731ef7a06b3398619dce5300, c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc, ba353caafb06ccee57b78d3254e3cebf1dea4a93 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < e451a904606c571f731ef7a06b3398619dce5300
Fixed in
  • e451a904606c571f731ef7a06b3398619dce5300
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc
Fixed in
  • c6a13ae00dab3a1a8c7cf2f843f0fc9e8d4b0ccc
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < ba353caafb06ccee57b78d3254e3cebf1dea4a93
Fixed in
  • ba353caafb06ccee57b78d3254e3cebf1dea4a93
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < 7097a0280b178237265681be66d1bef11d15894b
Fixed in
  • 7097a0280b178237265681be66d1bef11d15894b
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < 896a9512d0d83c2a4b357e5585b7b62a8e3f95c1
Fixed in
  • 896a9512d0d83c2a4b357e5585b7b62a8e3f95c1
LinuxLinuxAffected
  • ≥ 33f11d16142b06588eedfc1dd8cf93790979a712, < 472aba2603ca74c4f7722cb0c0296942b0776b8d
Fixed in
  • 472aba2603ca74c4f7722cb0c0296942b0776b8d

Description

In the Linux kernel, the following vulnerability has been resolved: ila: reload IPv6 header after pskb_may_pull in checksum adjust ila_csum_adjust_transport() caches ip6h = ipv6_hdr(skb) before calling pskb_may_pull(). On a non-linear skb whose transport header sits in a page fragment, pskb_may_pull() can call __pskb_pull_tail() / pskb_expand_head() and free the old skb head, leaving ip6h dangling; the following get_csum_diff(ip6h, p) then reads freed memory. ila_update_ipv6_locator() 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 ila_update_ipv6_locator() (KASAN). The route or mapping requires CAP_NET_ADMIN to configure, but trigger packets are unauthenticated once it exists. Reload ip6h after each pskb_may_pull() in ila_csum_adjust_transport() before the csum-diff read. In ila_update_ipv6_locator() only the ILA_CSUM_ADJUST_TRANSPORT 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.

References

Community reviews

Loading reviews…