Is this vulnerability remotely exploitable?

No, this is a local vulnerability. An attacker must already have the ability to run code on the affected system to open the driver's device and issue crafted IOCTL requests.

What level of access does an attacker need to exploit this issue?

The attacker typically only needs a standard, non-administrative user account with permission to access the driver's device interface. No kernel-mode or administrative privileges are required to trigger the vulnerable IOCTL handler.

What is the safest general fix pattern for developers of similar drivers?

The safest pattern is to remove or tightly restrict raw physical memory access from user-accessible IOCTLs, enforce strict privilege checks for any high-impact operations, and define secure ACLs on the device object so that only trusted, privileged components can invoke sensitive functionality.

Severity:

HIGH RISK

(7.3)

Missing Access Control in IOCTL Handler (CWE-269) in Ludashi Driver Physical Memory Interface

CVE-2025-67246

Published:

Jan 15, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Improper Access Control

CWE:

CWE-269;CWE-732

Impact:

Local Information Disclosure and Privilege Escalation Primitive

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Access Control

CWE:

CWE-269;CWE-732

Impact:

Local Information Disclosure and Privilege Escalation Primitive

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Missing Access Control in IOCTL Handler (CWE-269) in Ludashi Driver Physical Memory Interface

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare