CVE-2025-4657
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA buffer overflow vulnerability was reported in the Lenovo Protection Driver, prior to version 5.1.1110.4231, used in Lenovo PC Manager, Lenovo Browser, and Lenovo App Store could allow a local attacker with elevated privileges to execute arbitrary code.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow vulnerability in the Lenovo Protection Driver (kernel-mode) prior to version 5.1.1110.4231 allows a local attacker with existing elevated privileges to execute arbitrary code via the overflow, potentially achieving full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Lenovo Protection Driver is installedOpen Windows Services (services.msc) and look for a service named 'Lenovo Protection Driver' or similar Lenovo driver service. Alternatively, run 'sc query' or check Device Manager under 'Lenovo' or look for loaded kernel drivers.Affected if The driver/service is present on the system
-
Find the driver file versionLocate the Lenovo Protection Driver file (typically a .sys file in C:\Windows\System32\drivers\ or a Lenovo program directory). Right-click the file, select Properties, and check the File Version field. Alternatively, use 'driverquery /v' or PowerShell 'Get-ItemProperty' on the driver file.Affected if The driver file exists and returns a version number
-
Compare installed version to affected rangeCompare the found version number to 5.1.1110.4231. The vulnerability affects versions prior to 5.1.1110.4231.Affected if The installed version is lower than 5.1.1110.4231
-
Verify driver is loaded and activeRun 'sc query lprot' (or the actual service name found) or check 'driverquery /v | findstr -i lenovo' to see if the driver is currently loaded in memory.Affected if The driver is currently loaded and running
The system is affected if the Lenovo Protection Driver is installed with a version lower than 5.1.1110.4231 and the driver is actively loaded.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Lenovo Protection Driver to version 5.1.1110.4231 or later across all affected systems (Lenovo PC Manager, Browser, App Store). Prioritize endpoints where the driver is loaded.
5.1.1110.4231
- Locate Lenovo PC Manager, Lenovo Browser, or Lenovo App Store on the affected system
- Open the application and navigate to the settings or help section
- Check the current version of Lenovo Protection Driver
- Download and install Lenovo Protection Driver version 5.1.1110.4231 or later from Lenovo's official support website (iknow.lenovo.com.cn)
- Restart the system to ensure the updated driver is fully applied
- Verify the installed version matches 5.1.1110.4231 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4657 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4657 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data