Memory corruption via unchecked rt-link frame length
Published Mar 27, 2024 · Updated Nov 4, 2025
Buffer overflow in RT-Thread through 5.0.2 allows remote authenticated users to corrupt memory through oversized rt-link data frames. The frame_send() function copies frame->data_len bytes from real_data into a 1,024-byte static send buffer without checking the total frame size. Reachability requires a low-privileged rt-link path; the public analysis establishes memory corruption but does not demonstrate a resulting crash or code execution.
Summary
What happened
Buffer overflow in RT-Thread through 5.0.2 allows remote authenticated users to corrupt memory through oversized rt-link data frames. The frame_send() function copies frame->data_len bytes from real_data into a 1,024-byte static send buffer without checking the total frame size. Reachability requires a low-privileged rt-link path; the public analysis establishes memory corruption but does not demonstrate a resulting crash or code execution.
The record
- CVE
- CVE-2024-25395
- Published
- Mar 27, 2024
- Updated
- Nov 4, 2025
- Vendor
- RT-Thread
- Product
- RT-Thread
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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