CVE-2023-53007

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tracing: Make sure trace_printk() can output as soon as it can be used<br /> <br /> Currently trace_printk() can be used as soon as early_trace_init() is<br /> called from start_kernel(). But if a crash happens, and<br /> "ftrace_dump_on_oops" is set on the kernel command line, all you get will<br /> be:<br /> <br /> [ 0.456075] -0 0dN.2. 347519us : Unknown type 6<br /> [ 0.456075] -0 0dN.2. 353141us : Unknown type 6<br /> [ 0.456075] -0 0dN.2. 358684us : Unknown type 6<br /> <br /> This is because the trace_printk() event (type 6) hasn&amp;#39;t been registered<br /> yet. That gets done via an early_initcall(), which may be early, but not<br /> early enough.<br /> <br /> Instead of registering the trace_printk() event (and other ftrace events,<br /> which are not trace events) via an early_initcall(), have them registered at<br /> the same time that trace_printk() can be used. This way, if there is a<br /> crash before early_initcall(), then the trace_printk()s will actually be<br /> useful.