Cyber Resilience

CVE-2025-5869

Memory Safety in Rt-Thread 5.1.0

Public PoCMemory Safety
Published
09 June 2025
Modified
17 June 2026
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS: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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0078 53th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2025-5869 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Rt-Thread Rt-Thread. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A vulnerability classified as critical was discovered in RT-Thread version 5.1.0. It resides in the sys_recvfrom function within the file rt-thread/components/lwp/lwp_syscall.c, where improper handling of the from argument results in memory corruption, corresponding to CWE-119. The issue carries a CVSS 4.0 score of 8.6, reflecting high impact on confidentiality, integrity, and availability.

An attacker with low privileges on an adjacent network can supply a crafted argument to the affected function, triggering memory corruption that may allow arbitrary code execution or system compromise within the RT-Thread environment. The attack requires no user interaction and benefits from low attack complexity.

The associated EPSS score remains low and unchanged at 0.0117, indicating no material increase in observed exploitation interest following disclosure. No details on patches or workarounds are provided in the available references.

EU & UK References

Vulnerability Data

A vulnerability, which was classified as critical, was found in RT-Thread 5.1.0. Affected is the function sys_recvfrom of the file rt-thread/components/lwp/lwp_syscall.c. The manipulation of the argument from leads to memory corruption.

CWE(s)
CWE-119

Related Threats

MITRE ATT&CK Enterprise Techniques

T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-5865Same product: Rt-Thread Rt-Thread
CVE-2025-6693Same product: Rt-Thread Rt-Thread
CVE-2025-5866Same product: Rt-Thread Rt-Thread
CVE-2025-5868Same product: Rt-Thread Rt-Thread
CVE-2024-25388Same product: Rt-Thread Rt-Thread
CVE-2024-25395Same product: Rt-Thread Rt-Thread
CVE-2024-25391Same product: Rt-Thread Rt-Thread
CVE-2024-24335Same product: Rt-Thread Rt-Thread
CVE-2024-24334Same product: Rt-Thread Rt-Thread
CVE-2024-25390Same product: Rt-Thread Rt-Thread

Affected Assets

rt-thread
rt-thread
5.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

SI-10 Information Input Validation partial match

Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.

SI-16 Memory Protection partial match

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

References