Vulnerability · Published Jun 18, 2025 · Assigned by Linux
CVE-2022-49975bpf: Don't redirect packets with invalid pkt_len
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: bpf: Don't redirect packets with invalid pkt_len Syzbot found an issue [1]: fq_codel_drop() try to drop a flow whitout any skbs, that is, the flow->head is null. The root cause, as the [2] says, is because that bpf_prog_test_run_skb() run a bpf prog which redirects empty skbs. So we should determine whether the length of the packet modified by bpf prog or others like bpf_prog_test is valid before forwarding it directly.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49975 |
| Debian:13 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49975 |
| Debian:14 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux | 5.15.0-57.63 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1027.31 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1030.37 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1030.37.1 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1026.33 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1024.29 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1012.16 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1022.25 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1023.28 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1025.30 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-57.63 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1015.15 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1026.32 | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1022.24 | UBUNTU-CVE-2022-49975 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49975 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49975 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5293efe62df81908f2e90c9820c7edcc8e61f5e9 – before 8b68e53d56697a59b5c53893b53f508bbdf272a05293efe62df81908f2e90c9820c7edcc8e61f5e9 – before 6204bf78b2a903b96ba43afff6abc0b04d6e04625293efe62df81908f2e90c9820c7edcc8e61f5e9 – before a75987714bd2d8e59840667a28e15c1fa5c475545293efe62df81908f2e90c9820c7edcc8e61f5e9 – before 72f2dc8993f10262092745a88cb2dd0fef094f235293efe62df81908f2e90c9820c7edcc8e61f5e9 – before fd1894224407c484f652ad456e1ce423e89bb3eb |
| Linux | Linux | 4.9 |
References
- https://git.kernel.org/stable/c/8b68e53d56697a59b5c53893b53f508bbdf272a0
- https://git.kernel.org/stable/c/6204bf78b2a903b96ba43afff6abc0b04d6e0462
- https://git.kernel.org/stable/c/a75987714bd2d8e59840667a28e15c1fa5c47554
- https://git.kernel.org/stable/c/72f2dc8993f10262092745a88cb2dd0fef094f23
- https://git.kernel.org/stable/c/fd1894224407c484f652ad456e1ce423e89bb3eb