CVE Catalog

CVE-2026-80846

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, the xfrm (ESP-in-TCP) module has an issue with packets that have no ingress device. When the ingress device is removed, dev_get_by_index_rcu() returns NULL, leading to a NULL dereference in the XFRM input path. The fix drops such packets.

Risk Assessment

The organization may experience system crashes (Oops) during network interface or namespace teardown, potentially affecting system stability.

Recommendation

Apply a Linux kernel update containing the fix that drops ESP-in-TCP packets when the ingress device cannot be resolved.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS