Filtered by vendor Eclipse
Subscriptions
Filtered by product Threadx
Subscriptions
Total
5 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-55079 | 1 Eclipse | 1 Threadx | 2025-10-22 | 5.5 Medium |
| In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service. | ||||
| CVE-2025-55080 | 1 Eclipse | 1 Threadx | 2025-10-22 | 7.1 High |
| In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write. | ||||
| CVE-2025-55078 | 1 Eclipse | 1 Threadx | 2025-10-21 | 5.5 Medium |
| In Eclipse ThreadX before version 6.4.3, an attacker can cause a denial of service (crash) by providing a pointer to a reserved or unmapped memory region. Vulnerable system calls had a check of pointers, but that check wasn't verifying whether the pointer is outside the module memory region. | ||||
| CVE-2024-2214 | 1 Eclipse | 1 Threadx | 2025-02-13 | 7 High |
| In Eclipse ThreadX before version 6.4.0, the _Mtxinit() function in the Xtensa port was missing an array size check causing a memory overwrite. The affected file was ports/xtensa/xcc/src/tx_clib_lock.c | ||||
| CVE-2024-2212 | 1 Eclipse | 1 Threadx | 2025-02-13 | 7.3 High |
| In Eclipse ThreadX before 6.4.0, xQueueCreate() and xQueueCreateSet() functions from the FreeRTOS compatibility API (utility/rtos_compatibility_layers/FreeRTOS/tx_freertos.c) were missing parameter checks. This could lead to integer wraparound, under-allocations and heap buffer overflows. | ||||
Page 1 of 1.