CVE-2026-23217

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> riscv: trace: fix snapshot deadlock with sbi ecall<br /> <br /> If sbi_ecall.c&amp;#39;s functions are traceable,<br /> <br /> echo "__sbi_ecall:snapshot" &gt; /sys/kernel/tracing/set_ftrace_filter<br /> <br /> may get the kernel into a deadlock.<br /> <br /> (Functions in sbi_ecall.c are excluded from tracing if<br /> CONFIG_RISCV_ALTERNATIVE_EARLY is set.)<br /> <br /> __sbi_ecall triggers a snapshot of the ringbuffer. The snapshot code<br /> raises an IPI interrupt, which results in another call to __sbi_ecall<br /> and another snapshot...<br /> <br /> All it takes to get into this endless loop is one initial __sbi_ecall.<br /> On RISC-V systems without SSTC extension, the clock events in<br /> timer-riscv.c issue periodic sbi ecalls, making the problem easy to<br /> trigger.<br /> <br /> Always exclude the sbi_ecall.c functions from tracing to fix the<br /> potential deadlock.<br /> <br /> sbi ecalls can easiliy be logged via trace events, excluding ecall<br /> functions from function tracing is not a big limitation.