Kernel crash via unchecked syscall array index
Published Jun 9, 2025 · Updated Jun 9, 2025
Improper array-index validation in RT-Thread 5.1.0 allows local users to crash the kernel through sys_thread_sigprocmask. The syscall passes the user-controlled how value directly to mask_command_u2k[how] without checking that the index is within the array bounds. A compromised user thread must invoke the syscall with an out-of-range value; the public report demonstrates a kernel-crash path but no working unauthorized-memory-access exploit.
Summary
What happened
Improper array-index validation in RT-Thread 5.1.0 allows local users to crash the kernel through sys_thread_sigprocmask. The syscall passes the user-controlled how value directly to mask_command_u2k[how] without checking that the index is within the array bounds. A compromised user thread must invoke the syscall with an out-of-range value; the public report demonstrates a kernel-crash path but no working unauthorized-memory-access exploit.
The record
- CVE
- CVE-2025-5868
- Published
- Jun 9, 2025
- Updated
- Jun 9, 2025
- Vendor
- RT-Thread
- Product
- RT-Thread
- Classifications
- CWE-119, CWE-129, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 9, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo