CVE-2026-99247

tracing: Do not initialize tracefs work if tracing is disabled

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Do not initialize tracefs work if tracing is disabled If trace buffer allocation fails during early boot (e.g. in early_trace_init() -> allocate_trace_buffers()), tracing_disabled is left set to 1 and the global trace array events list remains uninitialized. Later during boot, tracer_init_tracefs() (invoked via fs_initcall) queues tracerfs_init_work asynchronously without checking if tracing was disabled. When tracer_init_tracefs_work_func() runs, it calls event_trace_init() and init_tracer_tracefs(&global_trace, NULL) unconditionally. This leads to __find_event_file() dereferencing an uninitialized tr->events list, causing an early boot NULL pointer dereference Oops: BUG: Kernel NULL pointer dereference on read at 0x00000010 Faulting instruction address: 0xc000000000485be0 Oops: Kernel access of bad area, sig: 7 [#1] ... NIP [c000000000485be0] __find_event_file+0x70/0x3c0 LR [c000000000448874] init_tracer_tracefs+0x274/0xc80 Call Trace: init_tracer_tracefs+0x274/0xc80 tracer_init_tracefs_work_func+0x50/0x320 process_one_work+0x1e8/0x5c0 worker_thread+0x1dc/0x3d0 kthread+0x194/0x1b0 start_kernel_thread+0x14/0x18 Check tracing_disabled at the beginning of tracer_init_tracefs_work_func() and return immediately if tracing is disabled or failed to initialize, preventing the crash.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
Linux
EPSS
0.161% likely to be exploited in the next 30 days, higher than 5.347% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding e8665e884e076d894f3eed8b9ea28e37a6448604 (affected)
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding e8cfcd7e60eaa3b0dea4d71c64499604e7081736 (affected)
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding afd38b10b1c6a5c5d6952b15b990596dab9684e6 (affected)
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding 813e18881c6472eb229a63180ff42c808e3e949b (affected)
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding 7539c61f522ff693d9565a0411386c2236e776cd (affected)
  • 6621a7004684bfcff5af4c8e4d37989941f42a6b up to but excluding b3b974008388ab59e44d764ba7a63c988fec2524 (affected)
LinuxLinux
  • Default status: affected
  • 5.19 (affected)
  • 0 up to but excluding 5.19 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 3 Nov 2026 Published

References