CVE-2025-5866
BaseFortify
Publication date: 2025-06-09
Last updated on: 2025-07-11
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rt-thread | rt-thread | 5.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-129 | The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-5866 is a critical vulnerability in RT-Thread version 5.1.0 affecting the sys_sigprocmask system call. The vulnerability arises because the 'how' parameter, which is passed from user space and used as an index into an internal array (mask_command_u2k), is not properly validated for bounds. This improper validation allows an attacker to cause out-of-bounds array access, leading to potential kernel crashes or unauthorized memory access. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by causing kernel crashes resulting in denial of service. Additionally, it may allow an attacker to read or write unauthorized kernel memory, potentially leading to privilege escalation. Overall, it affects the confidentiality, integrity, and availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of CVE-2025-5866 involves monitoring for abnormal behavior related to the sys_sigprocmask system call in RT-Thread 5.1.0, such as kernel crashes or unusual memory access patterns. Since the vulnerability arises from improper validation of the 'how' parameter used as an array index, detection could include auditing system call usage and checking for out-of-bounds parameter values. However, no specific detection commands or signatures are provided in the available resources. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding use of the vulnerable RT-Thread 5.1.0 version or replacing the affected component with an alternative product, as no known countermeasures or patches currently exist. Restricting user access to prevent untrusted input to the sys_sigprocmask system call and monitoring for exploitation attempts may help reduce risk until a fix is available. [3]