Skip to content
Fencer Vulns
medium 5.5

CVE-2022-50253 json

bpf: make sure skb->len != 0 when redirecting to a tunneling device

published 2025-09-15 13 mo ago modified 2026-11-05 3 d ago also EUVD-2022-55499

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

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?

Patch / fix

  • Linux Linux 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2
  • linux Debian 14, Debian 13, Debian 12 6.1.4-1

debian advisories DEBIAN-CVE-2022-50253

  • linux Ubuntu 18.04 LTS 4.15.0-208.220
  • linux Ubuntu 20.04 LTS 5.4.0-144.161
  • linux Ubuntu 22.04 LTS 5.15.0-69.76
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1153.166
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1097.105
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1033.37
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1101.110
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1031.38

ubuntu advisories UBUNTU-CVE-2022-50253

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
  • kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
  • kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1
  • kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-38.1.21.15
  • kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
  • kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-39.1
  • kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1
  • kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.61.1

suse advisories SUSE-SU-2026:20473-1SUSE-SU-2026:20496-1SUSE-SU-2026:20039-1SUSE-SU-2026:20059-1SUSE-SU-2025:4521-1SUSE-SU-2025:4517-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.8.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.8.1
  • kernel-kvmsmall openSUSE Leap 16.0 6.12.0-160000.8.1

opensuse advisories openSUSE-SU-2025:20172-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-50253 updated cvss 4.4

kernel: Linux kernel: Denial of Service in network packet redirection

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.