CVE-2025-1115

Kernel-memory disclosure via unvalidated syscall name pointer

Published Feb 8, 2025 · Updated Feb 16, 2025

Information disclosure in RT-Thread Smart 5.1.0 and earlier allows local users to read kernel memory through crafted LWP syscall arguments. In sys_thread_create, lwp_syscall.c passes the user-supplied arg[0] name pointer directly to rt_thread_create without validating that it references user memory. Low-privileged local code is required, and the documented consequence is disclosure of sensitive kernel data without integrity or availability impact.

CVSS severity4.8
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in RT-Thread Smart 5.1.0 and earlier allows local users to read kernel memory through crafted LWP syscall arguments. In sys_thread_create, lwp_syscall.c passes the user-supplied arg[0] name pointer directly to rt_thread_create without validating that it references user memory. Low-privileged local code is required, and the documented consequence is disclosure of sensitive kernel data without integrity or availability impact.

The record

CVE
CVE-2025-1115
Published
Feb 8, 2025
Updated
Feb 16, 2025
Vendor
RT-Thread
Product
RT-Thread
Classifications
CWE-200, T1005
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 8, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 16, 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.

  1. Affected versionversion=5.0
  2. Affected versionversion=5.1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

RT-Thread · RT-Threadversion=5.0; version=5.1

Published CVSS scores

3.3VulDBCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
3.3VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
1.7VulDBAV:L/AC:L/Au:S/C:P/I:N/A:N
4.8VulDBCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1005Data from Local System

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