Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 1909df2d066424767429e13053eb9701263430ef, 31e4be21dacee49395013caae28576484a049a4f, 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1909df2d066424767429e13053eb9701263430ef, 31e4be21dacee49395013caae28576484a049a4f, 6776efe4a52f289a3fc18f8adf19b035a7d8e1bb; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-89565

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.9affected
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before 1909df2d066424767429e13053eb9701263430efaffected · git
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before c4dc23de4cc75e4e304170b31bb8aeeacd5cb990affected · git
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before 6d8c5b266d0035a061573843a7243be068eb6118affected · git
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before 31e4be21dacee49395013caae28576484a049a4faffected · git
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before fd01f1a3ed4a189a784654f7c69eb565872f2e12affected · git
    • cfc7381b3002756b1dcada32979e942aa3126e31 and later · before 6776efe4a52f289a3fc18f8adf19b035a7d8e1bbaffected · git
    • before 4.9not affected · semver
    • 6.1.188 and later · up to and including 6.1.*not affected · semver
    • 6.6.157 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89563Sep 11, 2026 · ip6_tunnel: use skb_cow_head() in ip6_tnl_xmit()
    31Monitor
  • ← EarlierCVE-2026-89564Sep 11, 2026 · ip: orphan prefetched skbs before multicast forwarding
    31Monitor
  • Later →CVE-2026-89566Sep 11, 2026 · jbd2: check need_resched() when skipping busy checkpoint buffers
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1909df2d066424767429e13053eb9701263430efVendor (CNA)
Linux Linux31e4be21dacee49395013caae28576484a049a4fVendor (CNA)
Linux Linux6776efe4a52f289a3fc18f8adf19b035a7d8e1bbVendor (CNA)
Linux Linux6d8c5b266d0035a061573843a7243be068eb6118Vendor (CNA)
Linux Linuxc4dc23de4cc75e4e304170b31bb8aeeacd5cb990Vendor (CNA)
Linux Linuxfd01f1a3ed4a189a784654f7c69eb565872f2e12Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records