CVE-2026-81002

CVE CVE-2026-81002EUVD EUVD-2026-76325Published 2026-09-11T19:42:55.000ZLast changed 2026-09-14T11:59:37.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: xdp: fix zero-copy frame layout xdp_convert_zc_to_xdp_frame() clones an XSK packet into an order-0 page and advertises PAGE_SIZE as its frame size. It allows the copied frame to occupy the page tail needed by skb_shared_info and records zero headroom even when metadata separates the frame header from packet data. An AF_XDP zero-copy packet redirected through cpumap can therefore make the skb overlap skb_shared_info or place it beyond the allocated page. Limit the copied layout to SKB_WITH_OVERHEAD(PAGE_SIZE) and include the metadata length in frame headroom. Redirect callers already handle a NULL conversion result. BUG: KASAN: slab-out-of-bounds in skb_gro_receive Write of size 4 at addr ffff88800cf37004 by task cpumap/1/map:1/146 Call Trace: skb_gro_receive (net/core/gro.c:174) udp_gro_receive (net/ipv4/udp_offload.c:812) inet_gro_receive (net/ipv4/af_inet.c:1539) dev_gro_receive (net/core/gro.c:515) gro_receive_skb (net/core/gro.c:633) cpu_map_kthread_run (kernel/bpf/cpumap.c:395) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:255) Kernel panic - not syncing: KASAN: panic_on_warn set ...

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <ced3e18cd9b9caf630aaa1e1eac305f5192ba896; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <444216dacdbebd3e52d5e704facafbb230da09e9; patch: 6.12.109; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <22092730129077c302d8c947bbe0876f0280c528; patch: 6.1.188; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <68d7cc5512238693670fc19c7a615df631e10edf; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <dcb6db9ca6515fcd3e00c93ec5e27dc7a0a7012f; patch: 7.2.4; patch: 7.3-rc1; patch: 5.10.270; patch: 6.18.50; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <6de17275b3ccdf9887568b07e54da2e3597217cf; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <71283aaa6c65b3cec84caf1dc78560985737641f; 4.20; patch: 0; b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 <15d1f3c0dbe7a740f779337deb39f23cd8d002c8; patch: 6.6.157; patch: 5.15.221

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.