Skip to content

CVE-2025-67246

Ludashi Driver privilege escalation

7.3 HIGHPublic exploitEPSS 0.16%
  1. Published15 Jan 2026

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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Affected products

Ludashi Driver< 5.1025

Remediation

Fixed in
Ludashi Driver≥ 5.1025

Frequently asked

Is CVE-2025-67246 being actively exploited?

CVE-2025-67246 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.16%.

How severe is CVE-2025-67246?

CVE-2025-67246 has a CVSS 3.1 base score of 7.3, rated high. EPSS estimates a 0.16% probability of exploitation.

Which products are affected by CVE-2025-67246?

Affected products include Ludashi Driver.

How do I fix CVE-2025-67246?

Upgrade affected software to a fixed version, for example Ludashi Driver 5.1025 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-67246 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.