Early-crash trace loss via late event registration
Published Mar 27, 2025 · Updated May 11, 2026
Denial of service in Linux kernel tracing allows local users to make early-crash trace_printk output unusable during an oops. The trace_printk event type remains unregistered until early_initcall even though trace_printk becomes usable during early_trace_init, so the dump reports Unknown type 6. The condition requires ftrace_dump_on_oops and a crash before early_initcall; it loses diagnostic trace output rather than causing the initiating crash.
Summary
What happened
Denial of service in Linux kernel tracing allows local users to make early-crash trace_printk output unusable during an oops. The trace_printk event type remains unregistered until early_initcall even though trace_printk becomes usable during early_trace_init, so the dump reports Unknown type 6. The condition requires ftrace_dump_on_oops and a crash before early_initcall; it loses diagnostic trace output rather than causing the initiating crash.
The record
- CVE
- CVE-2023-53007
- Published
- Mar 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.12
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <198c83963f6335ca6d690cff067679560f2a3a22
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <b0af180514edea6c83dc9a299d9f383009c99f25
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <b94d7c7654356860dd7719120c7d15ba38b6162a
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <de3930a4883ddad2244efd6d349013294c62c75c
- Affected versionversion=e725c731e3bb1e892e7b564c945b121cb41d1087 <f97eb0ab066133483a65c93eb894748de2f6b598
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo