[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2022-50253":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2022-50253","In the Linux kernel, the following vulnerability has been resolved:  bpf: make sure skb->len != 0 when redirecting to a tunneling device  syzkaller managed to trigger another case where skb->len == 0 when we enter __dev_queue_xmit:  WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 skb_assert_len include/linux/skbuff.h:2576 [inline] WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 __dev_queue_xmit+0x2069/0x35e0 net/core/dev.c:4295  Call Trace:  dev_queue_xmit+0x17/0x20 net/core/dev.c:4406  __bpf_tx_skb net/core/filter.c:2115 [inline]  __bpf_redirect_no_mac net/core/filter.c:2140 [inline]  __bpf_redirect+0x5fb/0xda0 net/core/filter.c:2163  ____bpf_clone_redirect net/core/filter.c:2447 [inline]  bpf_clone_redirect+0x247/0x390 net/core/filter.c:2419  bpf_prog_48159a89cb4a9a16+0x59/0x5e  bpf_dispatcher_nop_func include/linux/bpf.h:897 [inline]  __bpf_prog_run include/linux/filter.h:596 [inline]  bpf_prog_run include/linux/filter.h:603 [inline]  bpf_test_run+0x46c/0x890 net/bpf/test_run.c:402  bpf_prog_test_run_skb+0xbdc/0x14c0 net/bpf/test_run.c:1170  bpf_prog_test_run+0x345/0x3c0 kernel/bpf/syscall.c:3648  __sys_bpf+0x43a/0x6c0 kernel/bpf/syscall.c:5005  __do_sys_bpf kernel/bpf/syscall.c:5091 [inline]  __se_sys_bpf kernel/bpf/syscall.c:5089 [inline]  __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5089  do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48  entry_SYSCALL_64_after_hwframe+0x61/0xc6  The reproducer doesn't really reproduce outside of syzkaller environment, so I'm taking a guess here. It looks like we do generate correct ETH_HLEN-sized packet, but we redirect the packet to the tunneling device. Before we do so, we __skb_pull l2 header and arrive again at skb->len == 0. Doesn't seem like we can do anything better than having an explicit check after __skb_pull?",null,[],[],[],[14],{"_key":15},"CVE-2022-50253",[],[],[],"2025-09-15T14:15:36.007Z","2026-04-28T20:25:31.559025Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2022-50253",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,52,55,56],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt5_10_178_1",true,"ecosystem","5.10.178-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt6_1_4_1","6.1.4-1",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9}]