CVE-2026-1652
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 potential buffer overflow vulnerability was reported in the Lenovo Virtual Bus driver used in Smart Connect that could allow a local authenticated user to corrupt memory and cause a Windows blue screen error.
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 confidenceA buffer overflow vulnerability exists in the Lenovo Virtual Bus driver (part of Smart Connect) that allows a local authenticated user to corrupt memory, leading to a Windows blue screen (BUGCODE_USB_DRIVER) error. The flaw stems from insufficient bounds checking in the driver when handling input data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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.
-
Verify Lenovo Virtual Bus driver presenceOpen Device Manager, expand 'System devices', and look for 'Lenovo Virtual Bus' or 'Lenovo Virtual Bus Driver' in the list. Alternatively, run 'driverquery /v' and search for 'LenovoVirtualBus' in the output.Affected if The driver is not listed in Device Manager or driverquery output, indicating the driver is not installed.
-
Identify the installed driver versionIn Device Manager, right-click the Lenovo Virtual Bus device, select Properties, go to the Driver tab, and note the Driver Version string. Alternatively, navigate to the driver file location (typically C:\Windows\System32\drivers\) and check file properties of 'LenovoVirtualBus.sys' if present.Affected if Driver version cannot be determined or the driver file is missing, preventing version comparison.
-
Confirm Smart Connect installationOpen Programs and Features in Control Panel or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Smart Connect*"}' via PowerShell to check if Smart Connect is installed, as Virtual Bus ships with it.Affected if Smart Connect is not installed, meaning the Virtual Bus driver component is unlikely to be present.
-
Inspect driver file detailsLocate 'LenovoVirtualBus.sys' in the Windows\System32\drivers folder, right-click the file, select Properties, and view the Details tab for version and file info. If the file does not exist, the driver is not loaded.Affected if The driver file LenovoVirtualBus.sys does not exist in the drivers directory.
-
Review system event logs for crash eventsOpen Event Viewer, navigate to Windows Logs\System, and filter for events with Source 'BugCheck' or search for events containing 'BUGCODE_USB_DRIVER' to identify any blue screen incidents that may correlate with this vulnerability.Affected if Recent BUGCODE_USB_DRIVER blue screen events are present in the system event log.
A user is affected if the Lenovo Virtual Bus driver is installed and the installed version falls within the vulnerable version range published by Lenovo for this CVE.
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.
From vendor dataApply the Lenovo-supplied driver update for the Virtual Bus driver. Until a patch is available, limit local user privileges and monitor system stability for crash events.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1652 — 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-2026-1652 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