CVE-2023-53007: tracing: Make sure trace_printk() can output as soon as it can be used
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 198c83963f6335ca6d690cff067679560f2a3a22, 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253, 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce.
Low priority for now. Upgrade to Linux Linux 198c83963f6335ca6d690cff067679560f2a3a22, 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253, 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 27, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.12 and later · before 4.14.305
- linux linux kernel4.15 and later · before 4.19.272
- linux linux kernel4.20 and later · before 5.4.231
- linux linux kernel5.5 and later · before 5.10.166
- linux linux kernel5.11 and later · before 5.15.91
- linux linux kernel5.16 and later · before 6.1.9
- linux linux kernel6.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 5.4.231 and later · up to and including 5.4.*not affected · semver
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before f97eb0ab066133483a65c93eb894748de2f6b598affected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before b94d7c7654356860dd7719120c7d15ba38b6162aaffected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ceaffected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before de3930a4883ddad2244efd6d349013294c62c75caffected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before b0af180514edea6c83dc9a299d9f383009c99f25affected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before 198c83963f6335ca6d690cff067679560f2a3a22affected · git
- e725c731e3bb1e892e7b564c945b121cb41d1087 and later · before 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253affected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.11-1 | 6.1.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53004Mar 27, 2025 · ovl: fix tmpfile leak22Monitor
- ← EarlierCVE-2023-53005Mar 27, 2025 · trace_events_hist: add check for return value of 'create_hist_field'22Monitor
- Later →CVE-2023-53008Mar 27, 2025 · cifs: fix potential memory leaks in session setup22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 198c83963f6335ca6d690cff067679560f2a3a22 | Vendor (CNA) |
| Linux Linux | 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253 | Vendor (CNA) |
| Linux Linux | 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce | Vendor (CNA) |
| Linux Linux | b0af180514edea6c83dc9a299d9f383009c99f25 | Vendor (CNA) |
| Linux Linux | b94d7c7654356860dd7719120c7d15ba38b6162a | Vendor (CNA) |
| Linux Linux | de3930a4883ddad2244efd6d349013294c62c75c | Vendor (CNA) |
| Linux Linux | f97eb0ab066133483a65c93eb894748de2f6b598 | Vendor (CNA) |
| debian:linux | 6.1.11-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253
- git.kernel.org/stable/c/76b2390fdc80c0a8300e5da5b6b62d201b6fe9ce
- git.kernel.org/stable/c/b0af180514edea6c83dc9a299d9f383009c99f25
- git.kernel.org/stable/c/b94d7c7654356860dd7719120c7d15ba38b6162a
- git.kernel.org/stable/c/de3930a4883ddad2244efd6d349013294c62c75c
- git.kernel.org/stable/c/f97eb0ab066133483a65c93eb894748de2f6b598
Vendor advisories and official records. Exploit/PoC links are deliberately left out.