CVE-2023-52879

tracing: Have trace_event_file have ref counters

MEDIUM
5.5
CVSS Score
Published: May 21, 2024 at 03:32 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Have trace_event_file have ref counters The following can crash the kernel: # cd /sys/kernel/tracing # echo 'p:sched schedule' > kprobe_events # exec 5>>events/kprobes/sched/enable # > kprobe_events # exec 5>&- The above commands: 1. Change directory to the tracefs directory 2. Create a kprobe event (doesn't matter what one) 3. Open bash file descriptor 5 on the enable file of the kprobe event 4. Delete the kprobe event (removes the files too) 5. Close the bash file descriptor 5 The above causes a crash! BUG: kernel NULL pointer dereference, address: 0000000000000028 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 877 Comm: bash Not tainted 6.5.0-rc4-test-00008-g2c6b6b1029d4-dirty #186 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:tracing_release_file_tr+0xc/0x50 What happens here is that the kprobe event creates a trace_event_file "file" descriptor that represents the file in tracefs to the event. It maintains state of the event (is it enabled for the given instance?). Opening the "enable" file gets a reference to the event "file" descriptor via the open file descriptor. When the kprobe event is deleted, the file is also deleted from the tracefs system which also frees the event "file" descriptor. But as the tracefs file is still opened by user space, it will not be totally removed until the final dput() is called on it. But this is not true with the event "file" descriptor that is already freed. If the user does a write to or simply closes the file descriptor it will reference the event "file" descriptor that was just freed, causing a use-after-free bug. To solve this, add a ref count to the event "file" descriptor as well as a new flag called "FREED". The "file" will not be freed until the last reference is released. But the FREE flag will be set when the event is removed to prevent any more modifications to that event from happening, even if there's still a reference to the event "file" descriptor.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.198 ≤ v < 5.10.2025.15.134 ≤ v < 5.15.1405.4.258 ≤ v < 5.4.2626.1.55 ≤ v < 6.1.646.5.5 ≤ v < 6.5.136.6 ≤ v < 6.6.16.6 ≤ v < 6.7407bf1c140f0757706c0b28604bcc90837d45ce25.10.1985.15.1345.4.2586.1.556.5.56.69beec04370132a7a6cd1aa9897f6fffc6262ff28a46bf337a20f9edd3c8041b025639842280d0575e6807c873d8791ae5a5186ad05ec66cab926539af5ca233e2e66dc1c249bf07eefa37e34a6c9346afa6d449e4d024d8c17f4288e0567d28ace69415c
Vendor states this is fixed in 2c9de867ca285c397cd71af703763fe416265706 (fixed)
Vendor states this is fixed in 2fa74d29fc1899c237d51bf9a6e132ea5c488976 (fixed)
Vendor states this is fixed in 9034c87d61be8cff989017740a91701ac8195a1d (fixed)
Vendor states this is fixed in 961c4511c7578d6b8f39118be919016ec3db1c1e (fixed)
Vendor states this is fixed in a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f (fixed)
Vendor states this is fixed in bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4 (fixed)
Vendor states this is fixed in cbc7c29dff0fa18162f2a3889d82eeefd67305e0 (fixed)
Vendor states this is fixed in 5.10.202 (unaffected)
Vendor states this is fixed in 5.15.140 (unaffected)
Vendor states this is fixed in 5.4.262 (unaffected)
Vendor states this is fixed in 6.1.64 (unaffected)
Vendor states this is fixed in 6.5.13 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.1 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)

References (7)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2c9de867ca285c397cd71af703763fe416265706
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2fa74d29fc1899c237d51bf9a6e132ea5c488976
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9034c87d61be8cff989017740a91701ac8195a1d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/961c4511c7578d6b8f39118be919016ec3db1c1e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cbc7c29dff0fa18162f2a3889d82eeefd67305e0

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card