| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in RT-Thread up to 5.1.0. This affects the function sys_device_open/sys_device_read/sys_device_control/sys_device_init/sys_device_close/sys_device_write of the file components/drivers/core/device.c. Performing a manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2025-6693. The attack must be initiated from a local position. There is no exploit available.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability, which was classified as critical, was found in RT-Thread up to 5.1.0. This affects the function sys_device_open/sys_device_read/sys_device_control/sys_device_init/sys_device_close/sys_device_write of the file components/drivers/core/device.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-6693. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/26/2025).
The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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/26/2025 🔍06/26/2025 🔍
06/26/2025 🔍
Sources
Product: github.comAdvisory: 10387/10388/10389/10390
Status: Not defined
CVE: CVE-2025-6693 (🔍)
GCVE (CVE): GCVE-0-2025-6693
GCVE (VulDB): GCVE-100-313959
Entry
Created: 06/26/2025 09:16Changes: 06/26/2025 09:16 (53)
Complete: 🔍
Submitter: Zephyr Saxon
Cache ID: 216::103
Submit
Accepted
- Submit #595813: RT-Thread 5.1.0 Code Injection (by Zephyr Saxon)
Duplicate
- Submit #XXXXXX: Xx-xxxxxx X.x.x Xxxxxxxxxxxx Xxxxxxx Xxxx Xxxxxxxxxx (by Zephyr Saxon)
- Submit #XXXXXX: Xx-xxxxxx X.x.x Xxxxxxxx Xxxxxxxx Xx Xxxxxxxxxx (by Zephyr Saxon)
- Submit #XXXXXX: Xx-xxxxxx X.x.x Xxxxxxxx Xxxxxxxx Xx Xxxxxxxxxx (by Zephyr Saxon)
- Submit #XXXXXX: Xx-xxxxxx X.x.x Xxxxxxxx Xxxxxxxx Xx Xxxxxxxxxx (by Zephyr Saxon)
- Submit #XXXXXX: Xx-xxxxxx X.x.x Xxxxxxxx Xxxxxxxx Xx Xxxxxxxxxx (by Zephyr Saxon)
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.