CVE-2023-53007
Last modified
CVE-2023-53007 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.12, < 4.14.305 | — |
| Linux | Linux Kernel | >= 4.15, < 4.19.272 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.231 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.166 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.91 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.9 | — |
| Linux | Linux Kernel | 6.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-53007?
How severe is CVE-2023-53007?
How do I fix CVE-2023-53007?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-53001Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53002In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53003In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53004In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53005In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53006In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53008In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5301A vulnerability classified as critical was found in DedeCMS …8.8
- CVE-2023-53010In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53011In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53012In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53007?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
