CVE-2023-53007None▾ SunlitIn 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()…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 5.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < f97eb0ab066133483a65c93eb894748de2f6b598Linux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < b94d7c7654356860dd7719120c7d15ba38b6162aLinux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < 76b2390fdc80c0a8300e5da5b6b62d201b6fe9ceLinux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < de3930a4883ddad2244efd6d349013294c62c75cLinux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < b0af180514edea6c83dc9a299d9f383009c99f25Linux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < 198c83963f6335ca6d690cff067679560f2a3a22Linux >= e725c731e3bb1e892e7b564c945b121cb41d1087 < 3bb06eb6e9acf7c4a3e1b5bc87aed398ff8e2253Linux 4.12Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses