CVE-2026-23217

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 9, 2026
No patch confirmed yet.
generic

riscv: trace: fix snapshot deadlock with sbi ecall - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1f8285bc8e3508c1fde23b5205f1270215d4984
generic

riscv: trace: fix snapshot deadlock with sbi ecall - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0d7f5f0c9f05f1b6d4ee7110f15bef9c11f9df0

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.10—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:50 UTCOSV refresh
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 23:57 UTCOSV refresh
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-14 09:48 UTCGHSA enrichment
Show 19 more
  1. 2026-08-13 02:07 UTCEG score recompute
  2. 2026-08-13 02:07 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 07:30 UTCGHSA enrichment
  5. 2026-08-09 14:09 UTCEG score recompute
  6. 2026-08-09 14:09 UTCGHSA enrichment
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-07 21:41 UTCGHSA enrichment
  9. 2026-08-06 03:35 UTCEG score recompute
  10. 2026-08-06 03:35 UTCGHSA enrichment
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 15:10 UTCEPSS rescore
  13. 2026-08-04 10:38 UTCEPSS rescore
  14. 2026-08-02 20:21 UTCEG score recompute
  15. 2026-08-02 20:21 UTCGHSA enrichment
  16. 2026-08-01 04:15 UTCEPSS rescore
  17. 2026-07-27 14:13 UTCEPSS rescore
  18. 2026-07-27 13:28 UTCEG score recompute
  19. 2026-07-27 13:28 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-23217?
CVE-2026-23217 is a medium vulnerability published on February 18, 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 "sbiecall:snapshot" > /sys/kernel/tracing/setftrace_filter may get the kernel into a deadlock. (Functions in sbi_ecall.c are excluded…
When was CVE-2026-23217 disclosed?
CVE-2026-23217 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23217 actively exploited?
CVE-2026-23217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.7% of all scored CVEs.
What is the CVSS score of CVE-2026-23217?
CVE-2026-23217 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23217

Explore →

Is Your Infrastructure Affected by CVE-2026-23217?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs