Answer in brief
CVE-2026-89565 records a Unknown severity vulnerability in ipip: fix skb leak in collect_md mode when metadata_dst allocation fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cfc7381b3002756b1dcada32979e942aa3126e31 <6d8c5b266d0035a061573843a7243be068eb6118 || >=cfc7381b3002756b1dcada32979e942aa3126e31 <31e4be21dacee49395013caae28576484a049a4f || >=cfc7381b3002756b1dcada32979e942aa3126e31 <fd01f1a3ed4a189a784654f7c69eb565872f2e12 || >=cfc7381b3002756b1dcada32979e942aa3126e31 <6776efe4a52f289a3fc18f8adf19b035a7d8e1bb | 6d8c5b266d0035a061573843a7243be068eb6118, 31e4be21dacee49395013caae28576484a049a4f, fd01f1a3ed4a189a784654f7c69eb565872f2e12, 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb |
| Linux/Linuxgeneric | 4.9 | Not reported |
| Linux/Linuxgeneric | >=cfc7381b3002756b1dcada32979e942aa3126e31 <1909df2d066424767429e13053eb9701263430ef || >=cfc7381b3002756b1dcada32979e942aa3126e31 <c4dc23de4cc75e4e304170b31bb8aeeacd5cb990 || >=cfc7381b3002756b1dcada32979e942aa3126e31 <6d8c5b266d0035a061573843a7243be068eb6118 || >=cfc7381b3002756b1dcada32979e942aa3126e31 <31e4be21dacee49395013caae28576484a049a4f || >=cfc7381b3002756b1dcada32979e942aa3126e31 <fd01f1a3ed4a189a784654f7c69eb565872f2e12 || >=cfc7381b3002756b1dcada32979e942aa3126e31 <6776efe4a52f289a3fc18f8adf19b035a7d8e1bb | 1909df2d066424767429e13053eb9701263430ef, c4dc23de4cc75e4e304170b31bb8aeeacd5cb990, 6d8c5b266d0035a061573843a7243be068eb6118, 31e4be21dacee49395013caae28576484a049a4f, fd01f1a3ed4a189a784654f7c69eb565872f2e12, 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.