Linux Kernel up to 6.4.7 trace_buffered_event_disable buffer overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$5k-$25k0.00

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.4.7. This vulnerability affects the function trace_buffered_event_disable. Executing a manipulation can lead to buffer overflow. This vulnerability appears as CVE-2023-54211. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.4.7. This vulnerability affects the function trace_buffered_event_disable. The manipulation with an unknown input leads to a buffer overflow vulnerability. The CWE definition for the vulnerability is CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2023-54211 since 12/30/2025. The exploitation appears to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 06/07/2026).

The vulnerability scanner Nessus provides a plugin with the ID 319480 (EulerOS Virtualization 2.10.1 : kernel (EulerOS-SA-2026-2022)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.322, 4.19.291, 5.4.253, 5.10.190, 5.15.124, 6.1.43 or 6.4.8 eliminates this vulnerability. Applying the patch 1488d782c9e43087a3f341b8186cd25f3cf75583/b4f4ab423107dc1ba8e9cc6488c645be6403d3f5/cdcc35e6454133feb61561b4e0d0c80e52cbc2ba/a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074/813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20/a3a3c7bddab9b6c5690b20796ef5e332b8c48afb/528c9d73153754defb748f0b96ad33308668d817/dea499781a1150d285c62b26659f62fb00824fce is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (319480) and CERT Bund (WID-SEC-2025-2941). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

  • Debian Linux
  • Amazon Linux 2
  • IBM Power Hardware Management Console
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • IBM DataPower Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 319480
Nessus Name: EulerOS Virtualization 2.10.1 : kernel (EulerOS-SA-2026-2022)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.322/4.19.291/5.4.253/5.10.190/5.15.124/6.1.43/6.4.8
Patch: 1488d782c9e43087a3f341b8186cd25f3cf75583/b4f4ab423107dc1ba8e9cc6488c645be6403d3f5/cdcc35e6454133feb61561b4e0d0c80e52cbc2ba/a6d2fd1703cdc8ecfc3e73987e0fb7474ae2b074/813cede7b2f5a4b1b75d2d4bb4e705cc8e063b20/a3a3c7bddab9b6c5690b20796ef5e332b8c48afb/528c9d73153754defb748f0b96ad33308668d817/dea499781a1150d285c62b26659f62fb00824fce

Timelineinfo

12/30/2025 Advisory disclosed
12/30/2025 +0 days CVE reserved
12/30/2025 +0 days VulDB entry created
06/07/2026 +159 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-54211 (🔒)
GCVE (CVE): GCVE-0-2023-54211
GCVE (VulDB): GCVE-100-338968
CERT Bund: WID-SEC-2025-2941 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 12/30/2025 16:46
Updated: 06/07/2026 03:05
Changes: 12/30/2025 16:46 (58), 01/01/2026 08:50 (7), 04/26/2026 16:23 (1), 06/07/2026 03:05 (2)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!