Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89565ipip: fix skb leak in collect_md mode when metadata_dst allocation fails

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < 1909df2d066424767429e13053eb9701263430ef
    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < c4dc23de4cc75e4e304170b31bb8aeeacd5cb990
    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < 6d8c5b266d0035a061573843a7243be068eb6118
    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < 31e4be21dacee49395013caae28576484a049a4f
    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < fd01f1a3ed4a189a784654f7c69eb565872f2e12
    • affected cfc7381b3002756b1dcada32979e942aa3126e31 – < 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89565 badge
[![CVE-2026-89565](https://cveledger.app/badge/CVE-2026-89565.svg)](https://cveledger.app/cve/CVE-2026-89565)

Record last updated .