cbcvebase.
CVE-2023-54211
published 2025-12-30

CVE-2023-54211: In the Linux kernel, the following vulnerability has been resolved: tracing: Fix warning in trace_buffered_event_disable() Warning happened in…

PriorityP421low3.3
EPSS
0.18%
8.1th percentile
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

21 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.52-1 (bookworm)linux 6.1.52-1 (bookworm)
linuxlinux——
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < 1488d782c9e43087a3f341b8186cd25f3cf755831488d782c9e43087a3f341b8186cd25f3cf75583
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < b4f4ab423107dc1ba8e9cc6488c645be6403d3f5b4f4ab423107dc1ba8e9cc6488c645be6403d3f5
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < cdcc35e6454133feb61561b4e0d0c80e52cbc2bacdcc35e6454133feb61561b4e0d0c80e52cbc2ba
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < 813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < a3a3c7bddab9b6c5690b20796ef5e332b8c48afba3a3c7bddab9b6c5690b20796ef5e332b8c48afb
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < 528c9d73153754defb748f0b96ad33308668d817528c9d73153754defb748f0b96ad33308668d817
linuxlinux>= 0fc1b09ff1ff404ddf753f5ffa5cd0adc8fdcdc9 < dea499781a1150d285c62b26659f62fb00824fcedea499781a1150d285c62b26659f62fb00824fce
linuxlinux_kernel>= 0 < 5.10.191-15.10.191-1
linuxlinux_kernel>= 0 < 6.1.52-16.1.52-1
linuxlinux_kernel>= 0 < 6.4.11-16.4.11-1
linuxlinux_kernel>= 0 < 6.4.11-16.4.11-1
linuxlinux_kernel>= 4.15.0 < 4.19.2914.19.291
linuxlinux_kernel>= 4.20.0 < 5.4.2535.4.253
linuxlinux_kernel>= 4.7.0 < 4.14.3224.14.322
linuxlinux_kernel>= 5.11.0 < 5.15.1245.15.124
linuxlinux_kernel>= 5.16.0 < 6.1.436.1.43
linuxlinux_kernel>= 5.5.0 < 5.10.1905.10.190
linuxlinux_kernel>= 6.2.0 < 6.4.86.4.8
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.