Vulnerability · Published Dec 30, 2025 · Assigned by Linux
CVE-2023-54173bpf: Disable preemption in bpf_event_output
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.2% (higher than 5% 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: Disable preemption in bpf_event_output We received report [1] of kernel crash, which is caused by using nesting protection without disabled preemption. The bpf_event_output can be called by programs executed by bpf_prog_run_array_cg function that disabled migration but keeps preemption enabled. This can cause task to be preempted by another one inside the nesting protection and lead eventually to two tasks using same perf_sample_data buffer and cause crashes like: BUG: kernel NULL pointer dereference, address: 0000000000000001 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page ... ? perf_output_sample+0x12a/0x9a0 ? finish_task_switch.isra.0+0x81/0x280 ? perf_event_output+0x66/0xa0 ? bpf_event_output+0x13a/0x190 ? bpf_event_output_data+0x22/0x40 ? bpf_prog_dfc84bbde731b257_cil_sock4_connect+0x40a/0xacb ? xa_load+0x87/0xe0 ? __cgroup_bpf_run_filter_sock_addr+0xc1/0x1a0 ? release_sock+0x3e/0x90 ? sk_setsockopt+0x1a1/0x12f0 ? udp_pre_connect+0x36/0x50 ? inet_dgram_connect+0x93/0xa0 ? __sys_connect+0xb4/0xe0 ? udp_setsockopt+0x27/0x40 ? __pfx_udp_push_pending_frames+0x10/0x10 ? __sys_setsockopt+0xdf/0x1a0 ? __x64_sys_connect+0xf/0x20 ? do_syscall_64+0x3a/0x90 ? entry_SYSCALL_64_after_hwframe+0x72/0xdc Fixing this by disabling preemption in bpf_event_output. [1] https://github.com/cilium/cilium/issues/26756
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.52-1 | DEBIAN-CVE-2023-54173 |
| Debian:13 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54173 |
| Debian:14 | linux | 6.4.11-1 | DEBIAN-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux | 5.15.0-88.98 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1049.54 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1051.59 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1051.59.1 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1046.54 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1046.51 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1032.38 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1042.45 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1045.51 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1046.51 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-88.98 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1040.40 | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1019.19 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1006.6 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1047.53 | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1042.45 | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2023-54173 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1025.29 | UBUNTU-CVE-2023-54173 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2a916f2f546ca1c1e3323e2a4269307f6d9890eb – before 3048cb0dc0cc9dc74ed93690dffef00733bcad5b2a916f2f546ca1c1e3323e2a4269307f6d9890eb – before c81bdf8f9f2b002d217c3d5357cdea9f2b82ff902a916f2f546ca1c1e3323e2a4269307f6d9890eb – before 36dd8ca330b76585640ed32255a3c99f901e15022a916f2f546ca1c1e3323e2a4269307f6d9890eb – before 063c9ce8e74e07bf94f99cd13146f42867875e8b2a916f2f546ca1c1e3323e2a4269307f6d9890eb – before d62cc390c2e99ae267ffe4b8d7e2e08b6c758c32 |
| Linux | Linux | 5.7 |
References
- https://git.kernel.org/stable/c/3048cb0dc0cc9dc74ed93690dffef00733bcad5b
- https://git.kernel.org/stable/c/c81bdf8f9f2b002d217c3d5357cdea9f2b82ff90
- https://git.kernel.org/stable/c/36dd8ca330b76585640ed32255a3c99f901e1502
- https://git.kernel.org/stable/c/063c9ce8e74e07bf94f99cd13146f42867875e8b
- https://git.kernel.org/stable/c/d62cc390c2e99ae267ffe4b8d7e2e08b6c758c32