CVE-2026-80792 Affecting linux-6.12 package, versions <6.12.107-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LINUX612-19964474
- published20 Sept 2026
- disclosed4 Sept 2026
Introduced: 4 Sep 2026
NewCVE-2026-80792 (opens in a new tab)How to fix?
Upgrade Echo:latest linux-6.12 to version 6.12.107-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.
References
- https://advisory.echohq.com/cve/CVE-2026-80792
- https://git.kernel.org/stable/c/087ee0d914aaae929f1660c9ca878e367655ba1a
- https://git.kernel.org/stable/c/3c770ac4e6f07af7c7b40c474a3efc61ffed7862
- https://git.kernel.org/stable/c/3dc98e5fe82d069dd29b124ffbdb679331dfea43
- https://git.kernel.org/stable/c/73a187384a8c8b983c7fea046d716b6752a1e7a3
- https://git.kernel.org/stable/c/75e0a544ebe9af663ef53ca21e9e9185c51fb54a
- https://git.kernel.org/stable/c/99219c82804f266189388e8bf1cf5135d10d5515
- https://git.kernel.org/stable/c/c95f01b78266828a57060d754fcbfc92123a98ed
- https://git.kernel.org/stable/c/d0d48d999b0eee6bb176ef4e39d9be868fa80f7e
- https://git.kernel.org/stable/c/d960881b9312e781a3429aabceb223ce6b7c882f