5.5

CVE-2023-53007: tracing: Make sure trace_printk() can output as soon as it can be used

Analyzed
AliasesUBUNTU-CVE-2023-53007DEBIAN-CVE-2023-53007
Published 27-03-2025Last modified 11-05-2026

Vulnerability summary

CVE-2023-53007 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.21% chance of exploitation in the next 30 days, higher than 10.9% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 5.5, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.21%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 5 · Related 5
SUSE-SU-2025:1176-1SUSE-SU-2025:1183-1SUSE-SU-2025:1195-1SUSE-SU-2025:1241-1SUSE-SU-2025:1293-1

Timeline

  1. 27-03-2025
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.21%

Chance of exploitation in the next 30 days

Percentile

11%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.20% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu112 products
  • linux< 4.15.0-209.220 | < 5.4.0-147.164 | < 5.15.0-70.77
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 4.15.0-1154.167 | < 5.4.0-1100.108 | < 5.15.0-1034.38
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < f97eb0ab066133483a65c93eb894748de2f6b598 | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < b94d7c7654356860dd7719120c7d15ba38b6162a | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < de3930a4883ddad2244efd6d349013294c62c75c | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < b0af180514edea6c83dc9a299d9f383009c99f25 | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < 198c83963f6335ca6d690cff067679560f2a3a22 | ≥ e725c731e3bb1e892e7b564c945b121cb41d1087, < 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253 | 4.12
  • linux_kernel≥ 4.12, < 4.14.305 | ≥ 4.15, < 4.19.272 | ≥ 4.20, < 5.4.231 | ≥ 5.5, < 5.10.166 | ≥ 5.11, < 5.15.91 | ≥ 5.16, < 6.1.9 | 6.2:rc1 | 6.2:rc2 | 6.2:rc3 | 6.2:rc4 | 6.2:rc5
Debian1 product
  • linux< 6.1.11-1

3 vendors · 115 products

References

11 links
Show all 11 references