Strix
63.3K

CVE-2026-80846

Unknown

Last modified

CVE-2026-80846 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 239d0f71af09dc2029fd4d730cb24b8c83aaa43a; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < f00235f9d12301183d61f75fbe4105506f3e5140; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 6af5cdb03819a5ce6e945992635c6c5e91045367; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 2dd1609cadff46c4b20ce53b91ab9cce1380456a; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < c296d25efbc840be24de83f56d43bc47e714ace9; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 328e40aa774b446969c69b654c52a051a95af8a1; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 7911e0236616487b89db6bd3ba3f408abd10eb23; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < 943d95233b8b4a88994e244fcf466f8c403d63f1; >= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, < e1d7c5ac1c246ce5775f604515de0a59fbf2116e
LinuxLinux5.6

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80846?
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.
How severe is CVE-2026-80846?
Severity scoring for CVE-2026-80846 is pending analysis.
How do I fix CVE-2026-80846?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80846?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST