Bug 2528647 (CVE-2026-80846) - CVE-2026-80846 kernel: xfrm: drop ESP-in-TCP packets with no ingress device
Summary: CVE-2026-80846 kernel: xfrm: drop ESP-in-TCP packets with no ingress device
Keywords:
Status: NEW
Alias: CVE-2026-80846
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-04 16:13 UTC by OSIDB Bzimport
Modified: 2026-10-21 13:50 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-04 16:13:05 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.