RT-Thread 5.1.0 lwp_syscall.c csys_sendto null pointer dereference
Summary
A vulnerability classified as critical was found in RT-Thread 5.1.0. The impacted element is the function csys_sendto of the file rt-thread/components/lwp/lwp_syscall.c. Executing a manipulation of the argument to can lead to null pointer dereference.
This vulnerability is handled as CVE-2025-5867. There is not any exploit available.
Details
A vulnerability classified as critical was found in RT-Thread 5.1.0. This vulnerability affects the function csys_sendto of the file rt-thread/components/lwp/lwp_syscall.c. The manipulation of the argument to with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is available at github.com. This vulnerability was named CVE-2025-5867. The exploitation appears to be easy. Technical details are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-17443). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.8
VulDB Base Score: 8.0
VulDB Temp Score: 7.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.0
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/08/2025 Advisory disclosed06/08/2025 VulDB entry created
06/09/2025 VulDB entry last update
Sources
Product: github.comAdvisory: 10299
Status: Not defined
CVE: CVE-2025-5867 (🔒)
GCVE (CVE): GCVE-0-2025-5867
GCVE (VulDB): GCVE-100-311626
EUVD: 🔒
Entry
Created: 06/08/2025 19:41Updated: 06/09/2025 11:22
Changes: 06/08/2025 19:41 (53), 06/09/2025 10:43 (30), 06/09/2025 11:22 (1)
Complete: 🔍
Submitter: Zephyr Saxon
Cache ID: 216::103
Submit
Accepted
- Submit #584129: RT-Thread 5.1.0 Improper Handling of Parameters (by Zephyr Saxon)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.