cve.bz

CVE-2025-8061 lenovo

7.3 highEPSS 0.4%

High (7.3) in lenovo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A potential insufficient access control vulnerability was reported in the Lenovo Dispatcher 3.0 and Dispatcher 3.1 drivers used by some Lenovo consumer notebooks that could allow an authenticated local user to execute code with elevated privileges. The Lenovo Dispatcher 3.2 driver is not affected. This vulnerability does not affect systems when the Windows feature Core Isolation Memory Integrity is enabled. Lenovo systems preloaded with Windows 11 have this feature enabled by default.

Severity

CVSS 4.0

7.3 high
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-09-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-782 Exposed IOCTL with Insufficient Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-8061 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-8061?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-8061?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-8061 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • lenovo:dispatcher 3.0 driver
  • lenovo:dispatcher 3.1 driver

Versions

From the CNA's record in the CVE List.

ProductAffected
Lenovo Dispatcher 3.0 Driverbefore 3.1.0.41
Lenovo Dispatcher 3.1 Driverbefore 3.1.0.41

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • symeonp/Lenovo-CVE-2025-8061 Harbor Check: matches CVE 127 stars, created
    PoC for popping a system shell against the LnvMSRIO.sys driver
  • spawn451/CVE-2025-8061-Exploit Harbor Check: matches CVE 18 stars, Pascal, created
    Exploit LnvMSRIO.sys vulnerable driver
  • uLl0a/MSRMapper Harbor Check: matches CVE 8 stars, created
    MSRMapper is a manual kernel driver mapper for Windows x64 that abuses CVE-2025-8061 in the vulnerable Lenovo driver LnvMSRIO.sys to perfor…
  • vxqs/Lenovo-CVE-2025-8061 Harbor Check: matches CVE 0 stars, C++, created
    My PoC of Lenovo-CVE-2025-8061

References

Check your stackJSON