CVE-2025-6693Public exploit

Kernel code execution via unchecked device callback

Published Jun 26, 2025 · Updated Jun 26, 2025

Memory corruption in RT-Thread 5.1.0 and earlier allows local users to execute code in kernel context through the generic device API. The sys_device_control path accepts a supplied device object and calls its ops->control function pointer after checking only that the pointer is non-null, without validating that it names a legitimate callback. A compromised low-privileged user thread can redirect control flow, elevate privileges, and compromise confidentiality, integrity, or availability.

CVSS severity8.5
High
EPSS probability0.27%
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

Memory corruption in RT-Thread 5.1.0 and earlier allows local users to execute code in kernel context through the generic device API. The sys_device_control path accepts a supplied device object and calls its ops->control function pointer after checking only that the pointer is non-null, without validating that it names a legitimate callback. A compromised low-privileged user thread can redirect control flow, elevate privileges, and compromise confidentiality, integrity, or availability.

The record

CVE
CVE-2025-6693
Published
Jun 26, 2025
Updated
Jun 26, 2025
Vendor
RT-Thread
Product
RT-Thread
Classifications
CWE-119, T0890
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 26, 2025CVE publishedPublication date reported by the CVE source.
  2. Jun 26, 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.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

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

Published CVSS scores

6.8INCIBE-CERTAV:L/AC:L/Au:S/C:C/I:C/A:C
8.5INCIBE-CERTCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
7.8INCIBE-CERTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 exploitPublished

Weakness, pattern, technique

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
T0890Exploitation for Privilege Escalation

Public exploit references

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