xdp: fix zero-copy frame layout
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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 ...
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in dcb6db9ca6515fcd3e00c93ec5e27dc7a0a7012f; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 22092730129077c302d8c947bbe0876f0280c528; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in ced3e18cd9b9caf630aaa1e1eac305f5192ba896; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 6de17275b3ccdf9887568b07e54da2e3597217cf; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 444216dacdbebd3e52d5e704facafbb230da09e9; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 15d1f3c0dbe7a740f779337deb39f23cd8d002c8; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 68d7cc5512238693670fc19c7a615df631e10edf; From b0d1beeff2a97a0cf1965ea8f1d13b8973f22582 · fixed in 71283aaa6c65b3cec84caf1dc78560985737641f
- Linux Linux
4.20
- KernelLinux
From 4.20.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/dcb6db9ca6515fcd3e00c93ec5e27dc7a0a7012f
- stable/c/22092730129077c302d8c947bbe0876f0280c528
- stable/c/ced3e18cd9b9caf630aaa1e1eac305f5192ba896
- stable/c/6de17275b3ccdf9887568b07e54da2e3597217cf
- stable/c/444216dacdbebd3e52d5e704facafbb230da09e9
- stable/c/15d1f3c0dbe7a740f779337deb39f23cd8d002c8
- stable/c/68d7cc5512238693670fc19c7a615df631e10edf
- stable/c/71283aaa6c65b3cec84caf1dc78560985737641f