ila: reload IPv6 header after pskb_may_pull in checksum adjust
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 33f11d16142b06588eedfc1dd8cf93790979a712 · < 472aba2603ca74c4f7722cb0c0296942b0776b8d| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s ILA checksum adjustment can use a stale IPv6 header pointer after pulling packet data. A remote, unauthenticated IPv6 packet can trigger a slab use-after-free when routed through a configured ILA checksum-adjust-transport route or receive-side mapping. Setting up that route or mapping requires CAP_NET_ADMIN; triggering the flaw afterward requires no authentication or user interaction.
Engineers running Linux kernels with a configured ILA checksum-adjust-transport route or receive-side mapping should check their systems; affected versions were not specified.