Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23217

riscv: trace: fix snapshot deadlock with sbi ecall

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.

Timeline

  1. ID reserved

    By Linux

  2. · 36 days later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23217, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f – < f8b8ec0ddde74066d4452a7a961da544f193e00f
    • affected 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f – < b1f8285bc8e3508c1fde23b5205f1270215d4984
    • affected 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f – < b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0
    • affected 82f134ddd4f5da11c277bd1aa02e2a733179725a
    • affected 6.10.10 – < 6.11
  • Linux · Linux

    • affected 6.11
    • unaffected < 6.11
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.10 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23217 badge
[![CVE-2026-23217](https://cveledger.app/badge/CVE-2026-23217.svg)](https://cveledger.app/cve/CVE-2026-23217)

Record last updated .