CVE-2026-89565

ipip: fix skb leak in collect_md mode when metadata_dst allocation fails

N/A
Published: September 11, 2026 at 07:44 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipip: fix skb leak in collect_md mode when metadata_dst allocation fails In collect_md mode ipip_tunnel_rcv() returns 0 without freeing the skb when ip_tun_rx_dst() fails to allocate the metadata_dst. ipip_rcv() and mplsip_rcv() are registered as xfrm_tunnel handlers, so tunnel4_rcv() and tunnelmpls4_rcv() read the zero return as "the packet has been consumed" and do not free it either. The skb is leaked. The other tunnel drivers all dispose of the packet at this point: ip6_tunnel.c jumps to its drop label, ip_gre.c and ip6_gre.c return PACKET_REJECT, which makes gre_rcv() free the skb. Only ipip returns 0. Jump to the existing drop label instead. It frees the skb and still returns 0, so the packet keeps being reported as consumed, which is what we want here: the outer header has already been pulled, and neither the remaining handlers nor an ICMP unreachable have any use for it. Triggering this needs an ipip or mplsip tunnel in collect_md mode and an atomic allocation failure, which is why it has gone unnoticed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.9cfc7381b3002756b1dcada32979e942aa3126e31
Vendor states this is fixed in 1909df2d066424767429e13053eb9701263430ef (fixed)
Vendor states this is fixed in 31e4be21dacee49395013caae28576484a049a4f (fixed)
Vendor states this is fixed in 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb (fixed)
Vendor states this is fixed in 6d8c5b266d0035a061573843a7243be068eb6118 (fixed)
Vendor states this is fixed in c4dc23de4cc75e4e304170b31bb8aeeacd5cb990 (fixed)
Vendor states this is fixed in fd01f1a3ed4a189a784654f7c69eb565872f2e12 (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card