CVE-2023-52879

Source
https://nvd.nist.gov/vuln/detail/CVE-2023-52879
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-52879.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2023-52879
Downstream
Related
Published
2024-05-21T15:32:11Z
Modified
2025-10-16T15:34:36.550798Z
Summary
tracing: Have trace_event_file have ref counters
Details

In the Linux kernel, the following vulnerability has been resolved:

tracing: Have traceeventfile have ref counters

The following can crash the kernel:

# cd /sys/kernel/tracing # echo 'p:sched schedule' > kprobeevents # exec 5>>events/kprobes/sched/enable # > kprobeevents # 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: errorcode(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:tracingreleasefiletr+0xc/0x50

What happens here is that the kprobe event creates a traceeventfile "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.

References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
e6807c873d8791ae5a5186ad05ec66cab926539a
Fixed
961c4511c7578d6b8f39118be919016ec3db1c1e
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
407bf1c140f0757706c0b28604bcc90837d45ce2
Fixed
a98172e36e5f1b3d29ad71fade2d611cfcc2fe6f
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
fa6d449e4d024d8c17f4288e0567d28ace69415c
Fixed
cbc7c29dff0fa18162f2a3889d82eeefd67305e0
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
a46bf337a20f9edd3c8041b025639842280d0575
Fixed
2fa74d29fc1899c237d51bf9a6e132ea5c488976
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
9beec04370132a7a6cd1aa9897f6fffc6262ff28
Fixed
2c9de867ca285c397cd71af703763fe416265706
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
f5ca233e2e66dc1c249bf07eefa37e34a6c9346a
Fixed
9034c87d61be8cff989017740a91701ac8195a1d
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
f5ca233e2e66dc1c249bf07eefa37e34a6c9346a
Fixed
bb32500fb9b78215e4ef6ee8b4345c5f5d7eafb4

Affected versions

v5.*

v5.10.198
v5.10.199
v5.10.200
v5.10.201
v5.15.134
v5.15.135
v5.15.136
v5.15.137
v5.15.138
v5.15.139
v5.4.258
v5.4.259
v5.4.260
v5.4.261

v6.*

v6.1.55
v6.1.56
v6.1.57
v6.1.58
v6.1.59
v6.1.60
v6.1.61
v6.1.62
v6.1.63
v6.5.10
v6.5.11
v6.5.12
v6.5.5
v6.5.6
v6.5.7
v6.5.8
v6.5.9
v6.6
v6.6-rc1
v6.6-rc2
v6.6-rc3
v6.6-rc4
v6.6-rc5
v6.6-rc6
v6.6-rc7

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.4.262
Type
ECOSYSTEM
Events
Introduced
5.5.0
Fixed
5.10.202
Type
ECOSYSTEM
Events
Introduced
5.11.0
Fixed
5.15.140
Type
ECOSYSTEM
Events
Introduced
5.16.0
Fixed
6.1.64
Type
ECOSYSTEM
Events
Introduced
6.2.0
Fixed
6.5.13
Type
ECOSYSTEM
Events
Introduced
6.6.0
Fixed
6.6.1