Vulnerability · Published Dec 30, 2025 · Assigned by Linux

CVE-2023-54211tracing: Fix warning in trace_buffered_event_disable()

Unrated

In plain English

A 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 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 88.5% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix warning in trace_buffered_event_disable() Warning happened in trace_buffered_event_disable() at WARN_ON_ONCE(!trace_buffered_event_ref) Call Trace: ? __warn+0xa5/0x1b0 ? trace_buffered_event_disable+0x189/0x1b0 __ftrace_event_enable_disable+0x19e/0x3e0 free_probe_data+0x3b/0xa0 unregister_ftrace_function_probe_func+0x6b8/0x800 event_enable_func+0x2f0/0x3d0 ftrace_process_regex.isra.0+0x12d/0x1b0 ftrace_filter_write+0xe6/0x140 vfs_write+0x1c9/0x6f0 [...] The cause of the warning is in __ftrace_event_enable_disable(), trace_buffered_event_enable() was called once while trace_buffered_event_disable() was called twice. Reproduction script show as below, for analysis, see the comments: ``` #!/bin/bash cd /sys/kernel/tracing/ # 1. Register a 'disable_event' command, then: # 1) SOFT_DISABLED_BIT was set; # 2) trace_buffered_event_enable() was called first time; echo 'cmdline_proc_show:disable_event:initcall:initcall_finish' > \ set_ftrace_filter # 2. Enable the event registered, then: # 1) SOFT_DISABLED_BIT was cleared; # 2) trace_buffered_event_disable() was called first time; echo 1 > events/initcall/initcall_finish/enable # 3. Try to call into cmdline_proc_show(), then SOFT_DISABLED_BIT was # set again!!! cat /proc/cmdline # 4. Unregister the 'disable_event' command, then: # 1) SOFT_DISABLED_BIT was cleared again; # 2) trace_buffered_event_disable() was called second time!!! echo '!cmdline_proc_show:disable_event:initcall:initcall_finish' > \ set_ftrace_filter ``` To fix it, IIUC, we can change to call trace_buffered_event_enable() at fist time soft-mode enabled, and call trace_buffered_event_disable() at last time soft-mode disabled.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.52-1DEBIAN-CVE-2023-54211
Debian:13linux6.4.11-1DEBIAN-CVE-2023-54211
Debian:14linux6.4.11-1DEBIAN-CVE-2023-54211
Ubuntu:22.04:LTSlinux5.15.0-88.98UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-aws5.15.0-1049.54UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure5.15.0-1051.59UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1051.59.1UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gcp5.15.0-1046.54UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gke5.15.0-1046.51UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1032.38UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-ibm5.15.0-1042.45UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1045.51UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-kvm5.15.0-1046.51UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-88.98UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1040.40UBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1019.19UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1006.6UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oracle5.15.0-1047.53UBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-raspi5.15.0-1042.45UBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-54211
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-54211

Affected products (as reported)

VendorProductVersions
Linux Linux 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before 1488d782c9e43087a3f341b8186cd25f3cf755830fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before b4f4ab423107dc1ba8e9cc6488c645be6403d3f50fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before cdcc35e6454133feb61561b4e0d0c80e52cbc2ba0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b0740fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before 813cede7b2f5a4b1b75d2d4bb4e705cc8e063b200fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before a3a3c7bddab9b6c5690b20796ef5e332b8c48afb0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before 528c9d73153754defb748f0b96ad33308668d8170fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 – before dea499781a1150d285c62b26659f62fb00824fce
Linux Linux 4.7

References