CVE-2026-80846

xfrm: drop ESP-in-TCP packets with no ingress device

N/A
Published: September 4, 2026 at 03:54 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: xfrm: drop ESP-in-TCP packets with no ingress device ESP-in-TCP receives records through the TCP strparser. handle_esp() restores skb->dev from the saved skb_iif before passing the packet into the XFRM input path. Queued TCP data can be processed after the original ingress device has been removed, for example during veth or net namespace teardown. In that case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input paths both expect skb->dev to be valid while building the route lookup, so queued ESP-in-TCP data can dereference a NULL device. Drop the packet if the saved ingress device can no longer be resolved. Such a packet can no longer be routed through the normal XFRM receive path, and this preserves the existing behaviour for packets whose ingress device still exists.

Affected

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

5.6e27cca96cd68fa2c6814c90f9a1cfd36bb68c593
Vendor states this is fixed in 239d0f71af09dc2029fd4d730cb24b8c83aaa43a (fixed)
Vendor states this is fixed in 2dd1609cadff46c4b20ce53b91ab9cce1380456a (fixed)
Vendor states this is fixed in 328e40aa774b446969c69b654c52a051a95af8a1 (fixed)
Vendor states this is fixed in 6af5cdb03819a5ce6e945992635c6c5e91045367 (fixed)
Vendor states this is fixed in 7911e0236616487b89db6bd3ba3f408abd10eb23 (fixed)
Vendor states this is fixed in 943d95233b8b4a88994e244fcf466f8c403d63f1 (fixed)
Vendor states this is fixed in c296d25efbc840be24de83f56d43bc47e714ace9 (fixed)
Vendor states this is fixed in e1d7c5ac1c246ce5775f604515de0a59fbf2116e (fixed)
Vendor states this is fixed in f00235f9d12301183d61f75fbe4105506f3e5140 (fixed)
Vendor states this is fixed in 5.10.269 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (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