Privilege escalation via unvalidated recvfrom pointer
Published Jun 9, 2025 · Updated Jun 9, 2025
Memory corruption in RT-Thread 5.1.0 allows local users to overwrite kernel memory through a crafted sys_recvfrom from pointer. The syscall passes the user-supplied pointer to sockaddr_tomusl, which performs memcpy after only a null check and never validates the destination as user memory. An unprivileged user process must invoke the syscall; a successful write can corrupt kernel state, escalate privileges, or crash the device.
Summary
What happened
Memory corruption in RT-Thread 5.1.0 allows local users to overwrite kernel memory through a crafted sys_recvfrom from pointer. The syscall passes the user-supplied pointer to sockaddr_tomusl, which performs memcpy after only a null check and never validates the destination as user memory. An unprivileged user process must invoke the syscall; a successful write can corrupt kernel state, escalate privileges, or crash the device.
The record
- CVE
- CVE-2025-5869
- Published
- Jun 9, 2025
- Updated
- Jun 9, 2025
- Vendor
- RT-Thread
- Product
- RT-Thread
- Classifications
- CWE-119, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo