Lenovo Dispatcher 3.0 Driver
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.1.0.41
Fixed in 3.1.0.41
- < 3.1.0.41
Fixed in 3.1.0.41
Mitigation
Update to the version (or newer) indicated for your model in the Product Impact section in the advisory: https://support.lenovo.com/us/en/product_security/LEN-200860
Timeline
Days relative to CVE publicationFirst public PoC 25 days after publication; not in CISA KEV. First PoC: symeonp/Lenovo-CVE-2025-8061 (created 6 Oct 2025, found by us: backfilled).
PoC repositories
Found on GitHub.2 PoCs · 3 suspicious or fake
PoCs 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| symeonp/Lenovo-CVE-2025-8061 | 6 Oct 2025 +25 d | 127 | PoC |
| vxqs/Lenovo-CVE-2025-8061 | 26 Apr 2026 +227 d | 0 | PoC via PoC Index |
Suspicious or fake 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| segura2010/lenovo-dispatcher-poc | 17 Nov 2025 +67 d | 5 | Fake |
| spawn451/CVE-2025-8061-Exploit | 10 Dec 2025 +90 d | 18 | Fake |
| uLl0a/MSRMapper | 17 Sep 2026 +1.0 y | 8 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.