Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67246: n/a

0
High
VulnerabilityCVE-2025-67246cvecve-2025-67246
Published: Thu Jan 15 2026 (01/15/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

A local information disclosure vulnerability exists in the Ludashi driver before 5.1025 due to a lack of access control in the IOCTL handler. This driver exposes a device interface accessible to a normal user and handles attacker-controlled structures containing the lower 4GB of physical addresses. The handler maps arbitrary physical memory via MmMapIoSpace and copies data back to user mode without verifying the caller's privileges or the target address range. This allows unprivileged users to read arbitrary physical memory, potentially exposing kernel data structures, kernel pointers, security tokens, and other sensitive information. This vulnerability can be further exploited to bypass the Kernel Address Space Layout Rules (KASLR) and achieve local privilege escalation.

AI-Powered Analysis

AILast updated: 01/15/2026, 16:17:38 UTC

Technical Analysis

CVE-2025-67246 is a local privilege escalation and information disclosure vulnerability found in the Ludashi driver versions before 5.1025. The root cause is a lack of proper access control in the driver's IOCTL handler, which exposes a device interface accessible to normal (unprivileged) users. The IOCTL handler processes attacker-controlled input structures that specify physical memory addresses within the lower 4GB range. The handler uses MmMapIoSpace to map arbitrary physical memory into the driver's address space and then copies this data back to user mode without verifying the caller's privileges or validating the target physical address range. This flaw allows an unprivileged local user to read arbitrary physical memory, potentially exposing sensitive kernel data such as kernel pointers, security tokens, and internal kernel data structures. By reading kernel memory, attackers can bypass Kernel Address Space Layout Randomization (KASLR), a key security mitigation that randomizes kernel memory layout to prevent exploitation. Bypassing KASLR can facilitate further local privilege escalation attacks, allowing attackers to gain higher privileges on the system. Although no public exploits are currently known, the vulnerability's nature makes it a significant risk in environments where local user access is possible. The vulnerability affects all systems running the vulnerable Ludashi driver versions, regardless of other mitigations, and requires local access but no user interaction beyond issuing the IOCTL request. The lack of a CVSS score indicates this is a newly published vulnerability, but the technical details suggest a high severity due to the potential for sensitive data exposure and privilege escalation.

Potential Impact

For European organizations, this vulnerability poses a significant risk to confidentiality and integrity of sensitive data and system security. Organizations with multi-user systems or environments where unprivileged users have local access—such as shared workstations, development machines, or enterprise endpoints—are particularly vulnerable. Exposure of kernel pointers and security tokens can lead to full system compromise if attackers leverage this flaw to escalate privileges. This can result in unauthorized access to sensitive corporate data, disruption of critical services, and potential lateral movement within networks. The ability to bypass KASLR undermines a fundamental kernel security mechanism, increasing the likelihood of successful exploitation of other vulnerabilities. Industrial, governmental, and financial sectors in Europe, which often rely on robust endpoint security, could face increased risk of targeted local attacks. The absence of known exploits in the wild provides a window for proactive mitigation, but the vulnerability's presence in widely deployed drivers could lead to rapid exploitation once public exploit code emerges.

Mitigation Recommendations

Immediate mitigation should focus on restricting local user access to systems running the vulnerable Ludashi driver. Organizations should implement strict access controls and limit physical and logical access to trusted users only. Monitor and audit usage of IOCTL calls and device interfaces related to the Ludashi driver to detect suspicious activity. Since no official patches are currently available, coordinate with the vendor or driver maintainers for timely updates and apply patches as soon as they are released. Employ endpoint protection solutions capable of detecting anomalous kernel memory access attempts. Consider deploying kernel integrity monitoring tools to detect unauthorized memory mappings or privilege escalation attempts. In environments where patching is delayed, use application whitelisting and privilege separation to reduce the attack surface. Educate users about the risks of local privilege escalation and enforce least privilege principles to minimize potential damage from compromised accounts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-08T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69690fc14c611209ad3adf0c

Added to database: 1/15/2026, 4:03:13 PM

Last enriched: 1/15/2026, 4:17:38 PM

Last updated: 1/15/2026, 5:28:56 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats