LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock affected RISC-V systems when tracing snapshots interact with SBI calls. The business impact is availability: a vulnerable host may hang under specific tracing conditions. There is no cited evidence of active exploitation, and the source does not describe remote exploitation.

Executive priority

Treat this as a targeted availability risk for RISC-V Linux infrastructure, not a broad enterprise emergency. Patch through normal kernel maintenance, accelerating where RISC-V systems support production workloads, tracing is used, or uptime requirements are strict.

Technical view

The bug is in RISC-V kernel tracing. If functions in sbi_ecall.c are traceable, an ftrace snapshot on __sbi_ecall can recursively trigger IPIs and SBI calls, causing an endless loop and kernel deadlock. The fix is to always exclude sbi_ecall.c functions from function tracing.

Likely exposure

Exposure appears limited to Linux on RISC-V kernels in the affected ranges, especially systems where function tracing snapshots are enabled. RISC-V systems without the SSTC extension may be easier to trigger because periodic timer clock events issue SBI ecalls.

Exploitation context

The bundle marks KEV as false and provides no cited active exploitation. The source describes a local tracing configuration condition, not a remote attack path. Privilege requirements are not stated in the provided sources, so teams should avoid assuming internet-exposed risk from this record alone.

Researcher notes

The record’s affected version data is sparse and somewhat hard to interpret. The clearest technical signal is the upstream stable fix: exclude SBI ecall implementation functions from function tracing to prevent recursive snapshot-triggered deadlock. No CVSS, CWE, or exploitability details are supplied.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Check distribution advisories for CVE-2026-23217 backports.
  • Avoid tracing snapshot configurations targeting SBI ecall functions until patched.
  • Prioritize RISC-V systems using affected kernel ranges.
  • Document any temporary tracing restrictions for operations teams.

Validation and detection

  • Inventory Linux RISC-V hosts and kernel versions.
  • Check kernel changelogs for CVE-2026-23217 or referenced commits.
  • Verify sbi_ecall.c functions are excluded from function tracing after update.
  • Regression-test tracing snapshots on representative RISC-V systems.
  • Confirm monitoring covers unexpected RISC-V host hangs or watchdog resets.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23217 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f, 1ff95eb2bebda50c4c5406caaf201e0fcb24cc8f, 82f134ddd4f5da11c277bd1aa02e2a733179725a, 6.10.10unaffected
LinuxLinux6.11, 0, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.