- Vulnerability/
- CVE-2023-53007
CVE-2023-53007: tracing: Make sure trace_printk() can output as soon as it can be used
First published: Thu Mar 27 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: tracing: Make sure trace_printk() can output as soon as it can be used Currently trace_printk() can be used as soon as early_trace_init() is called from start_kernel(). But if a crash happens, and "ftrace_dump_on_oops" is set on the kernel command line, all you get will be: [ 0.456075] <idle>-0 0dN.2. 347519us : Unknown type 6 [ 0.456075] <idle>-0 0dN.2. 353141us : Unknown type 6 [ 0.456075] <idle>-0 0dN.2. 358684us : Unknown type 6 This is because the trace_printk() event (type 6) hasn't been registered yet. That gets done via an early_initcall(), which may be early, but not early enough. Instead of registering the trace_printk() event (and other ftrace events, which are not trace events) via an early_initcall(), have them registered at the same time that trace_printk() can be used. This way, if there is a crash before early_initcall(), then the trace_printk()s will actually be useful.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/f97eb0ab066133483a65c93eb894748de2f6b598
- https://git.kernel.org/stable/c/b94d7c7654356860dd7719120c7d15ba38b6162a
- https://git.kernel.org/stable/c/76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce
- https://git.kernel.org/stable/c/de3930a4883ddad2244efd6d349013294c62c75c
- https://git.kernel.org/stable/c/b0af180514edea6c83dc9a299d9f383009c99f25
- https://git.kernel.org/stable/c/198c83963f6335ca6d690cff067679560f2a3a22
- https://git.kernel.org/stable/c/3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253
Frequently Asked Questions
What is the severity of CVE-2023-53007?
The severity of CVE-2023-53007 is considered medium, as it can lead to information leakage in the Linux kernel.
How do I fix CVE-2023-53007?
To fix CVE-2023-53007, users should update their Linux kernel to a version that includes the fix for this vulnerability.
What systems are affected by CVE-2023-53007?
CVE-2023-53007 affects various versions of the Linux kernel used across many Linux distributions.
What are the potential consequences of CVE-2023-53007?
Potential consequences of CVE-2023-53007 include the possibility of exposing sensitive information during kernel crashes.
Is CVE-2023-53007 being actively exploited in the wild?
As of now, there are no public reports indicating that CVE-2023-53007 is being actively exploited.
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/first-publish-date
- agent/references
- agent/type
- agent/description
- agent/title
- agent/last-modified-date
- agent/author
- agent/source
- agent/event
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/linux
- canonical/linux kernel