CVE-2023-53007

published 27 Mar 2025 · updated 7 Nov 2026

tracing: Make sure trace_printk() can output as soon as it can be used

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4.14.305, Kernel 4.19.272, Kernel 5.4.231 and 10 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=4.12 <4.14.305, >=4.15 <4.19.272, >=4.20 <5.4.231, >=5.11 <5.15.91, >=5.16 <6.1.9, >=5.5 <5.10.166, =6.2, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <b0af180514edea6c83dc9a299d9f383009c99f25, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <b94d7c7654356860dd7719120c7d15ba38b6162a, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <de3930a4883ddad2244efd6d349013294c62c75c, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <f97eb0ab066133483a65c93eb894748de2f6b598, =4.12, >=e725c731e3bb1e892e7b564c945b121cb41d1087 <198c83963f6335ca6d690cff067679560f2a3a224.14.305, 4.19.272, 5.4.231, 5.15.91, 6.1.9, 5.10.166, 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253, 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce, b0af180514edea6c83dc9a299d9f383009c99f25, b94d7c7654356860dd7719120c7d15ba38b6162a, de3930a4883ddad2244efd6d349013294c62c75c, f97eb0ab066133483a65c93eb894748de2f6b598, 198c83963f6335ca6d690cff067679560f2a3a22
linux-kernel: Kernel>=4.12.0 <4.14.305, >=4.15.0 <4.19.272, >=4.20.0 <5.4.231, >=5.11.0 <5.15.91, >=5.16.0 <6.1.9, >=5.5.0 <5.10.1664.14.305, 4.19.272, 5.4.231, 5.15.91, 6.1.9, 5.10.166

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53007 severity on Zeptric[![CVE-2023-53007](https://zeptric.io/badge/cve/CVE-2023-53007.svg)](https://zeptric.io/cve/CVE-2023-53007)