Answer in brief
CVE-2026-23217 records a Unknown severity vulnerability in riscv: trace: fix snapshot deadlock with sbi ecall. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f <f8b8ec0ddde74066d4452a7a961da544f193e00f || >=1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f <b1f8285bc8e3508c1fde23b5205f1270215d4984 || >=1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f <b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0 || 82f134ddd4f5da11c277bd1aa02e2a733179725a || >=6.10.10 <6.11 | f8b8ec0ddde74066d4452a7a961da544f193e00f, b1f8285bc8e3508c1fde23b5205f1270215d4984, b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0, 6.11 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Feb 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.