tracing: Make sure trace_printk() can output as soon as it can be used
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] -0 0dN.2. 347519us : Unknown type 6 [ 0.456075] -0 0dN.2. 353141us : Unknown type 6 [ 0.456075] -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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.305, 4.19.272, 5.10.166, 5.15.91, 5.4.231, 6.1.9
- CVEs
- CVE-2023-53007
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 04:45 UTC · Revision 1
Source evidence
tracing: Make sure trace_printk() can output as soon as it can be used
core-osv · Original sourcePublished 27 Mar 2025, 16:43 UTC
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] -0 0dN.2. 347519us : Unknown type 6 [ 0.456075] -0 0dN.2. 353141us : Unknown type 6 [ 0.456075] -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.
osv:CVE-2023-53007
Kernel
Fixed versions: 4.14.305, 4.19.272, 5.4.231, 5.10.166, 5.15.91, 6.1.9
Complete source record
{
"id": "b5ee45fbc07f60fbc0e8269127ad9b2ca30bcc6e8f2eb3032261f7829bc0aae7",
"url": "https://osv.dev/vulnerability/CVE-2023-53007",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "tracing: Make sure trace_printk() can output as soon as it can be used",
"summary": "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] -0 0dN.2. 347519us : Unknown type 6 [ 0.456075] -0 0dN.2. 353141us : Unknown type 6 [ 0.456075] -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.",
"evidence": "osv:CVE-2023-53007",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.305",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.272",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.231",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.166",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.91",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2023-53007",
"aliases": [
"CVE-2023-53007"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "e725c731e3bb1e892e7b564c945b121cb41d1087"
},
{
"fixed": "f97eb0ab066133483a65c93eb894748de2f6b598"
},
{
"fixed": "b94d7c7654356860dd7719120c7d15ba38b6162a"
},
{
"fixed": "76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce"
},
{
"fixed": "de3930a4883ddad2244efd6d349013294c62c75c"
},
{
"fixed": "b0af180514edea6c83dc9a299d9f383009c99f25"
},
{
"fixed": "198c83963f6335ca6d690cff067679560f2a3a22"
},
{
"fixed": "3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53007.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.12.0"
},
{
"fixed": "4.14.305"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.272"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.231"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.166"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.91"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53007.json"
}
}
],
"modified": "2026-10-28T02:30:49.909504398Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/198c83963f6335ca6d690cff067679560f2a3a22",
"https://git.kernel.org/stable/c/3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253",
"https://git.kernel.org/stable/c/76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce",
"https://git.kernel.org/stable/c/b0af180514edea6c83dc9a299d9f383009c99f25",
"https://git.kernel.org/stable/c/b94d7c7654356860dd7719120c7d15ba38b6162a",
"https://git.kernel.org/stable/c/de3930a4883ddad2244efd6d349013294c62c75c",
"https://git.kernel.org/stable/c/f97eb0ab066133483a65c93eb894748de2f6b598",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53007.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53007",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53007.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53007",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 518239,
"published_at": "2025-03-27T16:43:38.102+00:00"
}