Answer in brief
CVE-2023-53007 records a Medium severity (CVSS 5.5) vulnerability in tracing: Make sure trace_printk() can output as soon as it can be used. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.2:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.2:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.2:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.2:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.2:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e725c731e3bb1e892e7b564c945b121cb41d1087 <f97eb0ab066133483a65c93eb894748de2f6b598 || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <b94d7c7654356860dd7719120c7d15ba38b6162a || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <de3930a4883ddad2244efd6d349013294c62c75c || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <b0af180514edea6c83dc9a299d9f383009c99f25 || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <198c83963f6335ca6d690cff067679560f2a3a22 || >=e725c731e3bb1e892e7b564c945b121cb41d1087 <3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253 | f97eb0ab066133483a65c93eb894748de2f6b598, b94d7c7654356860dd7719120c7d15ba38b6162a, 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce, de3930a4883ddad2244efd6d349013294c62c75c, b0af180514edea6c83dc9a299d9f383009c99f25, 198c83963f6335ca6d690cff067679560f2a3a22, 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253 |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
Mar 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.