Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2023-53368— tracing: Fix race issue between cpu buffer write and swap

EPSS 0.01% · P2
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2023-53368

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
tracing: Fix race issue between cpu buffer write and swap
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race issue between cpu buffer write and swap Warning happened in rb_end_commit() at code: if (RB_WARN_ON(cpu_buffer, !local_read(&cpu_buffer->committing))) WARNING: CPU: 0 PID: 139 at kernel/trace/ring_buffer.c:3142 rb_commit+0x402/0x4a0 Call Trace: ring_buffer_unlock_commit+0x42/0x250 trace_buffer_unlock_commit_regs+0x3b/0x250 trace_event_buffer_commit+0xe5/0x440 trace_event_buffer_reserve+0x11c/0x150 trace_event_raw_event_sched_switch+0x23c/0x2c0 __traceiter_sched_switch+0x59/0x80 __schedule+0x72b/0x1580 schedule+0x92/0x120 worker_thread+0xa0/0x6f0 It is because the race between writing event into cpu buffer and swapping cpu buffer through file per_cpu/cpu0/snapshot: Write on CPU 0 Swap buffer by per_cpu/cpu0/snapshot on CPU 1 -------- -------- tracing_snapshot_write() [...] ring_buffer_lock_reserve() cpu_buffer = buffer->buffers[cpu]; // 1. Suppose find 'cpu_buffer_a'; [...] rb_reserve_next_event() [...] ring_buffer_swap_cpu() if (local_read(&cpu_buffer_a->committing)) goto out_dec; if (local_read(&cpu_buffer_b->committing)) goto out_dec; buffer_a->buffers[cpu] = cpu_buffer_b; buffer_b->buffers[cpu] = cpu_buffer_a; // 2. cpu_buffer has swapped here. rb_start_commit(cpu_buffer); if (unlikely(READ_ONCE(cpu_buffer->buffer) != buffer)) { // 3. This check passed due to 'cpu_buffer->buffer' [...] // has not changed here. return NULL; } cpu_buffer_b->buffer = buffer_a; cpu_buffer_a->buffer = buffer_b; [...] // 4. Reserve event from 'cpu_buffer_a'. ring_buffer_unlock_commit() [...] cpu_buffer = buffer->buffers[cpu]; // 5. Now find 'cpu_buffer_b' !!! rb_commit(cpu_buffer) rb_end_commit() // 6. WARN for the wrong 'committing' state !!! Based on above analysis, we can easily reproduce by following testcase: ``` bash #!/bin/bash dmesg -n 7 sysctl -w kernel.panic_on_warn=1 TR=/sys/kernel/tracing echo 7 > ${TR}/buffer_size_kb echo "sched:sched_switch" > ${TR}/set_event while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & while [ true ]; do echo 1 > ${TR}/per_cpu/cpu0/snapshot done & ``` To fix it, IIUC, we can use smp_call_function_single() to do the swap on the target cpu where the buffer is located, so that above race would be avoided.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于cpu缓冲区写入和交换之间存在竞争条件,可能导致警告触发。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux f1affcaaa861f27752a769f889bf1486ebd301fe ~ 90e037cabc2c2dfc39b3dd9c5b22ea91f995539a -
LinuxLinux 3.10 -

II. Public POCs for CVE-2023-53368

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53368

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-17 · 56 CVEs total

CVE-2022-50370i2c: designware: Fix handling of real but unexpected device interrupts
CVE-2022-50355staging: vt6655: fix some erroneous memory clean-up loops
CVE-2022-50358brcmfmac: return error when getting invalid max_flowrings from dongle
CVE-2022-50356net: sched: sfb: fix null pointer access issue when sfb_init() fails
CVE-2022-50357usb: dwc3: core: fix some leaks in probe
CVE-2022-50359media: cx88: Fix a null-ptr-deref bug in buffer_prepare()
CVE-2022-50354drm/amdkfd: Fix kfd_process_device_init_vm error handling
CVE-2022-50367fs: fix UAF/GPF bug in nilfs_mdt_destroy
CVE-2022-50368drm/msm/dsi: fix memory corruption with too many bridges
CVE-2022-50369drm/vkms: Fix null-ptr-deref in vkms_release()
CVE-2022-50366powercap: intel_rapl: fix UBSAN shift-out-of-bounds issue
CVE-2022-50371led: qcom-lpg: Fix sleeping in atomic
CVE-2022-50372cifs: Fix memory leak when build ntlmssp negotiate blob failed
CVE-2022-50373fs: dlm: fix race in lowcomms
CVE-2022-50374Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure
CVE-2023-53335RDMA/cxgb4: Fix potential null-ptr-deref in pass_establish()
CVE-2023-53336media: ipu-bridge: Fix null pointer deref on SSDB/PLD parsing warnings
CVE-2023-53337nilfs2: do not write dirty data after degenerating to read-only
CVE-2023-53338lwt: Fix return values of BPF xmit ops
CVE-2023-53339btrfs: fix BUG_ON condition in btrfs_cancel_balance

Showing top 20 of 56 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2023-53368

No comments yet


Leave a comment