Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53007

tracing: Make sure trace_printk() can output as soon as it can be used

Medium5.5EPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2023-53007, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < f97eb0ab066133483a65c93eb894748de2f6b598
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < b94d7c7654356860dd7719120c7d15ba38b6162a
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < de3930a4883ddad2244efd6d349013294c62c75c
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < b0af180514edea6c83dc9a299d9f383009c99f25
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < 198c83963f6335ca6d690cff067679560f2a3a22
    • affected e725c731e3bb1e892e7b564c945b121cb41d1087 – < 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.14.305 – ≤ 4.14.*
    • unaffected 4.19.272 – ≤ 4.19.*
    • unaffected 5.4.231 – ≤ 5.4.*
    • unaffected 5.10.166 – ≤ 5.10.*
    • unaffected 5.15.91 – ≤ 5.15.*
    • unaffected 6.1.9 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53007 badge
[![CVE-2023-53007](https://trackcve.app/badge/CVE-2023-53007.svg)](https://trackcve.app/cve/CVE-2023-53007)

Record last updated .