CVE-2026-80792

ipv6: fix use-after-free in ip6_finish_output2()

N/A
Published: September 4, 2026 at 03:13 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: ipv6: fix use-after-free in ip6_finish_output2() ip6_finish_output2() caches a pointer to the IPv6 destination address (daddr) before invoking lwtunnel_xmit(). The LWT-BPF transmit path or other encapsulation operations within lwtunnel_xmit() can reallocate the skb head, freeing the memory that daddr points to. When lwtunnel_xmit() returns LWTUNNEL_XMIT_CONTINUE, the function continues to use the stale daddr pointer to compute the nexthop and to look up or create the neighbour entry. This results in a use-after-free read, which can leak sensitive kernel data, pollute the neighbour table with arbitrary values, misdirect traffic, or crash the system. Fix this by re-fetching the IPv6 header and the destination address pointer after lwtunnel_xmit() returns LWTUNNEL_XMIT_CONTINUE, ensuring that the subsequent nexthop computation and neighbour lookup operate on valid memory.

Affected

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

1598154fd28ffa4a55beae1970475fd6776554b64132c4ad00ddbf3a175ea0d2c775b662a32f4c855.10.2335.155.4.289e415ed3a4b8b246ee5e9d109ff5153efcf96b9f2
Vendor states this is fixed in 087ee0d914aaae929f1660c9ca878e367655ba1a (fixed)
Vendor states this is fixed in 3c770ac4e6f07af7c7b40c474a3efc61ffed7862 (fixed)
Vendor states this is fixed in 3dc98e5fe82d069dd29b124ffbdb679331dfea43 (fixed)
Vendor states this is fixed in 73a187384a8c8b983c7fea046d716b6752a1e7a3 (fixed)
Vendor states this is fixed in 75e0a544ebe9af663ef53ca21e9e9185c51fb54a (fixed)
Vendor states this is fixed in 99219c82804f266189388e8bf1cf5135d10d5515 (fixed)
Vendor states this is fixed in c95f01b78266828a57060d754fcbfc92123a98ed (fixed)
Vendor states this is fixed in d0d48d999b0eee6bb176ef4e39d9be868fa80f7e (fixed)
Vendor states this is fixed in d960881b9312e781a3429aabceb223ce6b7c882f (fixed)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (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