Vulnerability in Linux
CVE-2026-23217
In the Linux kernel, the following vulnerability has been resolved: riscv: trace: fix snapshot deadlock with sbi ecall If sbi_ecall.c's functions are traceable, echo "__sbi_ecall:snapshot" > /sys/kernel/tracing/set_ftrace_filter may get the kernel into a deadlock. (Functions in sbi_ecall.c are excluded from tracing if CONFIG_RISCV_ALTERNATIVE_EARLY is set.) __sbi_ecall triggers a snapshot of the ringbuffer. The snapshot code raises an IPI interrupt, which results in another call to __sbi_ecall and another snapshot... All it takes to get into this endless loop is one initial __sbi_ecall. On RISC-V systems without SSTC extension, the clock events in timer-riscv.c issue periodic sbi ecalls, making the problem easy to trigger. Always exclude the sbi_ecall.c functions from tracing to fix the potential deadlock. sbi ecalls can easiliy be logged via trace events, excluding ecall functions from function tracing is not a big limitation.
EPSS: 0.001 (0.2th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Affected products
- Linux — versions 6.18.10, 6.19, 82f134ddd4f5da11c277bd1aa02e2a733179725a
- Linux Linux_kernel — versions 6.11, 6.19
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-23217?
- CVE-2026-23217 is a medium-severity vulnerability in Linux, classified under Improper Locking. CVSS score: 5.5/10. Published 2026-02-18.
- How severe is CVE-2026-23217?
- Medium severity. CVSS v3 base score is 5.5 out of 10.