Code execution via assertion-only address length check
Published Jul 18, 2025 · Updated Jul 18, 2025
Buffer overflow in RIOT through 2025.04 allows attackers to crash devices or execute code via an oversized link-layer address. The l2filter_add() function relies on an assertion to bound addr_len, then passes that value to memcpy() into the fixed-size list[i].addr buffer. Exploitation requires attacker-controlled input to reach l2filter_add() in a build with assertions disabled, and the resulting overwrite affects the RIOT device.
Summary
What happened
Buffer overflow in RIOT through 2025.04 allows attackers to crash devices or execute code via an oversized link-layer address. The l2filter_add() function relies on an assertion to bound addr_len, then passes that value to memcpy() into the fixed-size list[i].addr buffer. Exploitation requires attacker-controlled input to reach l2filter_add() in a build with assertions disabled, and the resulting overwrite affects the RIOT device.
The record
- CVE
- CVE-2025-53888
- Published
- Jul 18, 2025
- Updated
- Jul 18, 2025
- Vendor
- RIOT-OS
- Product
- RIOT
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 18, 2025CVE publishedPublication date reported by the CVE source.
- Jul 18, 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=<= 2025.04
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