CVE-2026-80846
xfrm: drop ESP-in-TCP packets with no ingress device
Reported by linux · Published September 4, 2026
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.
EPSS 0.19% · 9.2th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | f00235f9d12301183d61f75fbe4105506f3e5140, e1d7c5ac1c246ce5775f604515de0a59fbf2116e, c296d25efbc840be24de83f56d43bc47e714ace9, 943d95233b8b4a88994e244fcf466f8c403d63f1, 7911e0236616487b89db6bd3ba3f408abd10eb23, 6af5cdb03819a5ce6e945992635c6c5e91045367, 328e40aa774b446969c69b654c52a051a95af8a1, 2dd1609cadff46c4b20ce53b91ab9cce1380456a, 239d0f71af09dc2029fd4d730cb24b8c83aaa43a |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 |
| Linux | Linux | 5.6, 0, 5.10.269 |
| Linux | Linux | 7.3, 0, 5.10.269 |
| linux | linux_kernel | 5.6, 5.6, 5.6 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80846
vulnetix vdb fixes CVE-2026-80846
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80846/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart