https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 10:03:02 +0000 https://vulnerability.circl.lu/vuln/cve-2026-23088 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Fix crash on synthetic stacktrace field usage</p> <p>When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred:</p> <p>~# cd /sys/kernel/tracing ~# echo &#39;s:stack unsigned long stack[];&#39; &gt; dynamic_events ~# echo &#39;hist:keys=prev_pid:s0=common_stacktrace if prev_state &amp; 3&#39; &gt;&gt; events/sched/sched_switch/trigger ~# echo &#39;hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)&#39; &gt;&gt; events/sched/sched_switch/trigger</p> <p>The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the &#34;stack&#34; synthetic event that has a stacktrace as its field (called &#34;stack&#34;).</p> <p>~# echo &#39;s:syscall_stack s64 id; unsigned long stack[];&#39; &gt;&gt; dynamic_events ~# echo &#39;hist:keys=common_pid:s2=stack&#39; &gt;&gt; events/synthetic/stack/trigger ~# echo &#39;hist:keys=common_pid:s3=$s2,i0=id:onmatch(synthetic.stack).trace(syscall_stack,$i0,$s3)&#39; &gt;&gt; events/raw_syscalls/sys_exit/trigger</p> <p>The above makes another synthetic event called &#34;syscall_stack&#34; that attaches the first synthetic event (stack) to the sys_exit trace event and records the stacktrace from the stack event with the id of the system call that is exiting.</p> <p>When enabling this event (or using it in a historgram):</p> <p>~# echo 1 &gt; events/s…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Fix crash on synthetic stacktrace field usage</p> <p>When creating a synthetic event based on an existing synthetic event that had a stacktrace field and the new synthetic event used that field a kernel crash occurred:</p> <p>~# cd /sys/kernel/tracing ~# echo &#39;s:stack unsigned long stack[];&#39; &gt; dynamic_events ~# echo &#39;hist:keys=prev_pid:s0=common_stacktrace if prev_state &amp; 3&#39; &gt;&gt; events/sched/sched_switch/trigger ~# echo &#39;hist:keys=next_pid:s1=$s0:onmatch(sched.sched_switch).trace(stack,$s1)&#39; &gt;&gt; events/sched/sched_switch/trigger</p> <p>The above creates a synthetic event that takes a stacktrace when a task schedules out in a non-running state and passes that stacktrace to the sched_switch event when that task schedules back in. It triggers the &#34;stack&#34; synthetic event that has a stacktrace as its field (called &#34;stack&#34;).</p> <p>~# echo &#39;s:syscall_stack s64 id; unsigned long stack[];&#39; &gt;&gt; dynamic_events ~# echo &#39;hist:keys=common_pid:s2=stack&#39; &gt;&gt; events/synthetic/stack/trigger ~# echo &#39;hist:keys=common_pid:s3=$s2,i0=id:onmatch(synthetic.stack).trace(syscall_stack,$i0,$s3)&#39; &gt;&gt; events/raw_syscalls/sys_exit/trigger</p> <p>The above makes another synthetic event called &#34;syscall_stack&#34; that attaches the first synthetic event (stack) to the sys_exit trace event and records the stacktrace from the stack event with the id of the system call that is exiting.</p> <p>When enabling this event (or using it in a historgram):</p> <p>~# echo 1 &gt; events/s…</p> https://vulnerability.circl.lu/vuln/cve-2026-23088