CVE-2025-67246: n/a
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 Analysis
Technical Summary
This vulnerability exists due to insufficient access control in the IOCTL handler of the Ludashi driver before version 5.1025. The driver exposes a device interface accessible to normal users and processes attacker-controlled structures referencing the lower 4GB of physical addresses. It uses MmMapIoSpace to map arbitrary physical memory and copies data back to user mode without verifying caller privileges or address ranges. This flaw allows local attackers to read arbitrary physical memory, potentially leaking kernel data structures, pointers, and security tokens. The information disclosure can be leveraged to bypass KASLR, increasing the risk of local privilege escalation.
Potential Impact
An unprivileged local user can read arbitrary physical memory, exposing sensitive kernel information including security tokens and kernel pointers. This compromises confidentiality and can facilitate bypassing KASLR protections. While direct privilege escalation is not guaranteed, the vulnerability significantly aids attackers in escalating privileges locally. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local user access to the affected driver and monitor for suspicious local activity. Avoid running untrusted code with local user privileges on affected systems.
CVE-2025-67246: n/a
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
Machine-generated threat intelligence
Technical Analysis
This vulnerability exists due to insufficient access control in the IOCTL handler of the Ludashi driver before version 5.1025. The driver exposes a device interface accessible to normal users and processes attacker-controlled structures referencing the lower 4GB of physical addresses. It uses MmMapIoSpace to map arbitrary physical memory and copies data back to user mode without verifying caller privileges or address ranges. This flaw allows local attackers to read arbitrary physical memory, potentially leaking kernel data structures, pointers, and security tokens. The information disclosure can be leveraged to bypass KASLR, increasing the risk of local privilege escalation.
Potential Impact
An unprivileged local user can read arbitrary physical memory, exposing sensitive kernel information including security tokens and kernel pointers. This compromises confidentiality and can facilitate bypassing KASLR protections. While direct privilege escalation is not guaranteed, the vulnerability significantly aids attackers in escalating privileges locally. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local user access to the affected driver and monitor for suspicious local activity. Avoid running untrusted code with local user privileges on affected systems.
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: 4/15/2026, 11:38:05 AM
Last updated: 5/9/2026, 9:32:18 AM
Views: 180
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.