# CVE-2025-67246: Information disclosure in n/a

> Unprivileged users can read arbitrary physical memory via the Ludashi driver, enabling KASLR bypass and local privilege escalation.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-c23h-wjw2-xvwf

## What is CVE-2025-67246?

CVE-2025-67246 is a high-severity vulnerability in n/a, published on 15 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-67246?

It affects 1 product.


Products: Ludashi Ludashi Driver.

## How do I fix CVE-2025-67246?

No fix has been published for CVE-2025-67246 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-67246 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67246 exists.

Public exploit code:

- CVE-2025-67246 (github_poc): https://github.com/CDipper/CVE-2025-67246

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67246 and fix it if it is affected.

What it is: CVE-2025-67246 is a high-severity vulnerability in n/a, published on 15 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67246 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67246/ (Markdown: https://insights.sbomify.com/CVE-2025-67246/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67246
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67246
- OSV: https://osv.dev/vulnerability/CVE-2025-67246

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67246/
Summaries are generated and may contain mistakes; the official description above is the record.