CVE-2023-54211 json
tracing: Fix warning in trace_buffered_event_disable()
published 10mo ago modified 4mo ago also EUVD-2023-60430
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.14.322, 4.19.291, 5.4.253, 5.10.190, 5.15.124, 6.1.43, 6.4.8, 6.5
- linux Debian 12 6.1.52-1
- linux Debian 14, Debian 13 6.4.11-1
debian advisories DEBIAN-CVE-2023-54211
- linux Ubuntu 20.04 LTS 5.4.0-169.187
- linux Ubuntu 22.04 LTS 5.15.0-88.98
- linux-aws Ubuntu 20.04 LTS 5.4.0-1116.126
- linux-aws Ubuntu 22.04 LTS 5.15.0-1049.54
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1120.129
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1046.54
- linux-gke Ubuntu 22.04 LTS 5.15.0-1046.51
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1063.68
ubuntu advisories UBUNTU-CVE-2023-54211
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:0617-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0411-1
- git.kernel.org/stable/c/1488d782c9e43087a3f341b8186cd25f3cf75583 commit
- git.kernel.org/stable/c/b4f4ab423107dc1ba8e9cc6488c645be6403d3f5 commit
- git.kernel.org/stable/c/cdcc35e6454133feb61561b4e0d0c80e52cbc2ba commit
- git.kernel.org/stable/c/a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074 commit
- git.kernel.org/stable/c/813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20 commit
- git.kernel.org/stable/c/a3a3c7bddab9b6c5690b20796ef5e332b8c48afb commit
- git.kernel.org/stable/c/528c9d73153754defb748f0b96ad33308668d817 commit
- git.kernel.org/stable/c/dea499781a1150d285c62b26659f62fb00824fce commit
Is CVE-2023-54211 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54211 updated cvss 3.3
kernel: tracing: Fix warning in trace_buffered_event_disable()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-16).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/1488d782c9e43087a3f341b8186cd25f3cf75583
- git.kernel.org /stable/c/b4f4ab423107dc1ba8e9cc6488c645be6403d3f5
- git.kernel.org /stable/c/cdcc35e6454133feb61561b4e0d0c80e52cbc2ba
- git.kernel.org /stable/c/a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074
- git.kernel.org /stable/c/813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20
- git.kernel.org /stable/c/a3a3c7bddab9b6c5690b20796ef5e332b8c48afb
- git.kernel.org /stable/c/528c9d73153754defb748f0b96ad33308668d817
- git.kernel.org /stable/c/dea499781a1150d285c62b26659f62fb00824fce
Sources
- CVE List CVE-2023-54211
- NVD CVE-2023-54211
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.