Vulnerability · Published Mar 27, 2025 · Assigned by Linux
CVE-2023-52928bpf: Skip invalid kfunc call in backtrack_insn
Medium 5.5
In plain English
A medium-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.2% (higher than 16% 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: Skip invalid kfunc call in backtrack_insn The verifier skips invalid kfunc call in check_kfunc_call(), which would be captured in fixup_kfunc_call() if such insn is not eliminated by dead code elimination. However, this can lead to the following warning in backtrack_insn(), also see [1]: ------------[ cut here ]------------ verifier backtracking bug WARNING: CPU: 6 PID: 8646 at kernel/bpf/verifier.c:2756 backtrack_insn kernel/bpf/verifier.c:2756 __mark_chain_precision kernel/bpf/verifier.c:3065 mark_chain_precision kernel/bpf/verifier.c:3165 adjust_reg_min_max_vals kernel/bpf/verifier.c:10715 check_alu_op kernel/bpf/verifier.c:10928 do_check kernel/bpf/verifier.c:13821 [inline] do_check_common kernel/bpf/verifier.c:16289 [...] So make backtracking conservative with this by returning ENOTSUPP. [1] https://lore.kernel.org/bpf/CACkBjsaXNceR8ZjkLG=dT3P=4A8SBsg0Z5h5PWLryF5=ghKq=g@mail.gmail.com/
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52928 |
| Debian:13 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52928 |
| Debian:14 | linux | 6.1.11-1 | DEBIAN-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux | 5.15.0-72.79 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1036.40 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1038.45 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1038.45.1 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1034.42 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1033.38 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1020.25 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1030.33 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1030.35 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1033.38 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-72.79 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1025.25 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1035.41 | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1029.31 | UBUNTU-CVE-2023-52928 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52928 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-52928 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e6ac2450d6dee3121cd8bbf2907b78a68a8a353d – before 6e2fac197de2c4c041bdd8982cffb104689113f1e6ac2450d6dee3121cd8bbf2907b78a68a8a353d – before 74eec8266f37aff609db6a2f2b093e56a11c28c4e6ac2450d6dee3121cd8bbf2907b78a68a8a353d – before d3178e8a434b58678d99257c0387810a24042fb6 |
| Linux | Linux | 5.13 |