CVE-2022-50253
Severity CVSS v4.0:
Pending analysis
Type:
Unavailable / Other
Publication date:
15/09/2025
Last modified:
15/09/2025
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
bpf: make sure skb->len != 0 when redirecting to a tunneling device<br />
<br />
syzkaller managed to trigger another case where skb->len == 0<br />
when we enter __dev_queue_xmit:<br />
<br />
WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 skb_assert_len include/linux/skbuff.h:2576 [inline]<br />
WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 __dev_queue_xmit+0x2069/0x35e0 net/core/dev.c:4295<br />
<br />
Call Trace:<br />
dev_queue_xmit+0x17/0x20 net/core/dev.c:4406<br />
__bpf_tx_skb net/core/filter.c:2115 [inline]<br />
__bpf_redirect_no_mac net/core/filter.c:2140 [inline]<br />
__bpf_redirect+0x5fb/0xda0 net/core/filter.c:2163<br />
____bpf_clone_redirect net/core/filter.c:2447 [inline]<br />
bpf_clone_redirect+0x247/0x390 net/core/filter.c:2419<br />
bpf_prog_48159a89cb4a9a16+0x59/0x5e<br />
bpf_dispatcher_nop_func include/linux/bpf.h:897 [inline]<br />
__bpf_prog_run include/linux/filter.h:596 [inline]<br />
bpf_prog_run include/linux/filter.h:603 [inline]<br />
bpf_test_run+0x46c/0x890 net/bpf/test_run.c:402<br />
bpf_prog_test_run_skb+0xbdc/0x14c0 net/bpf/test_run.c:1170<br />
bpf_prog_test_run+0x345/0x3c0 kernel/bpf/syscall.c:3648<br />
__sys_bpf+0x43a/0x6c0 kernel/bpf/syscall.c:5005<br />
__do_sys_bpf kernel/bpf/syscall.c:5091 [inline]<br />
__se_sys_bpf kernel/bpf/syscall.c:5089 [inline]<br />
__x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5089<br />
do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48<br />
entry_SYSCALL_64_after_hwframe+0x61/0xc6<br />
<br />
The reproducer doesn&#39;t really reproduce outside of syzkaller<br />
environment, so I&#39;m taking a guess here. It looks like we<br />
do generate correct ETH_HLEN-sized packet, but we redirect<br />
the packet to the tunneling device. Before we do so, we<br />
__skb_pull l2 header and arrive again at skb->len == 0.<br />
Doesn&#39;t seem like we can do anything better than having<br />
an explicit check after __skb_pull?
Impact
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/07ec7b502800ba9f7b8b15cb01dd6556bb41aaca
- https://git.kernel.org/stable/c/1b65704b8c08ae92db29f720d3b298031131da53
- https://git.kernel.org/stable/c/5d3f4478d22b2cb1810f6fe0f797411e9d87b3e5
- https://git.kernel.org/stable/c/6d935a02658be82585ecb39aab339faa84496650
- https://git.kernel.org/stable/c/772431f30ca040cfbf31b791d468bac6a9ca74d3
- https://git.kernel.org/stable/c/e6a63203e5a90a39392fa1a7ffc60f5e9baf642a
- https://git.kernel.org/stable/c/f186303845a01cc7e991f9dc51d7e5a3cdc7aedb
- https://git.kernel.org/stable/c/ffbccc5fb0a67424e12f7f8da210c04c8063f797



