CVE-2023-53007 Details
Description
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.
A vulnerability in the Linux kernel's tracing mechanism has been addressed. The issue arose because the 'trace_printk()' function could be used prematurely, before all necessary trace events were registered. This was problematic if a crash occurred and 'ftrace_dump_on_oops' was enabled, as the unregistered 'trace_printk()' events would not provide useful information. The vulnerability has been resolved by ensuring that trace events are registered at the appropriate time, allowing 'trace_printk()' to be effective even if a crash happens early in the boot process.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/198c83963f6335ca6d690cff067679560f2a3a22 | kernel.org | Patch |
| https://git.kernel.org/stable/c/3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253 | kernel.org | Patch |
| https://git.kernel.org/stable/c/76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce | kernel.org | Patch |
| https://git.kernel.org/stable/c/b0af180514edea6c83dc9a299d9f383009c99f25 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b94d7c7654356860dd7719120c7d15ba38b6162a | kernel.org | Patch |
| https://git.kernel.org/stable/c/de3930a4883ddad2244efd6d349013294c62c75c | kernel.org | Patch |
| https://git.kernel.org/stable/c/f97eb0ab066133483a65c93eb894748de2f6b598 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.12, < 4.14.305 >= 4.15, < 4.19.272 >= 4.20, < 5.4.231 >= 5.5, < 5.10.166 >= 5.11, < 5.15.91 >= 5.16, < 6.1.9 6.2 rc1 6.2 rc2 6.2 rc3 6.2 rc4 6.2 rc5 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 30, 2025 | Initial Analysis | [email protected] |
| Mar 27, 2025 | New CVE Received | kernel.org |