CVE-2026-99140

tracing: Fix hist trigger timestamps for buffered events

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix hist trigger timestamps for buffered events Syzkaller triggered a WARN_ON_ONCE(!nest) warning: WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp Call trace: ring_buffer_event_time_stamp hist_field_timestamp hist_fn_call event_hist_trigger event_triggers_call __event_trigger_test_discard trace_event_buffer_commit do_trace_event_raw_event_sched_switch trace_event_raw_event_sched_switch The warning is probabilistically reproducible and is related to syzkaller executing the following commands: echo 'prev_pid == 999999' > events/sched/sched_switch/filter echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger The specific triggering process is as follows: CPU 0 CPU 1 (context switching) (echo 'hist:keys=common_timestamp' > \ events/sched/sched_switch/trigger) do_trace_event_raw_event_##call trace_event_buffer_lock_reserve if (!tr->no_filter_buffering_ref && trace_file->flags & EVENT_FILE_FL_FILTERED) return entry; // return directly event_hist_trigger_parse hist_register_trigger tracing_set_filter_buffering(file->tr, true); tr->no_filter_buffering_ref++; __trace_buffer_lock_reserve rb_start_commit local_inc(&cpu_buffer->committing); // skipped and not executed trace_event_buffer_commit __event_trigger_test_discard event_triggers_call event_hist_trigger hist_fn_call hist_field_timestamp ring_buffer_event_time_stamp nest = local_read(&cpu_buffer->committing); WARN_ON_ONCE(!nest) // trigger warning The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest). tracing_event_time_stamp() was added by commit d8279bfc5e959 ("tracing: Add tracing_event_time_stamp() API") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.

Key facts

Published
28 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.173% likely to be exploited in the next 30 days, higher than 6.834% 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
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding b3a94a79047d3fc9385b3709cb2b86f4a26ed0c3 (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding 71c5c7420478d94d6eb0b427f66fa41bbda651e3 (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding ab320f6aa3769480f735ed0ad026c4a61799b7bc (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding af192a356e9830a0df231b590ad6fb1fc28c9315 (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding 09c7cce2e59e6b3b1807520bcb1980c561f15d1e (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding 89e90b16aadd6e66bd0323bc8dfc76a62e756b57 (affected)
  • b94bc80df64823e676b506f8de7dcf6a688d681e up to but excluding 9414ca3b99e5a7f1f3bf51c2a01b383e1b355dd0 (affected)
LinuxLinux
  • Default status: affected
  • 5.13 (affected)
  • 0 up to but excluding 5.13 (unaffected)
  • 5.15.224 up to and including 5.15.* (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. 28 Oct 2026 Published

References