dbcve.org
Thinkpad X1 Fold Gen 1 FirmwareOperating system · Lenovo

CVE-2022-1108

MEDIUM · 6.7 CVSS v3.1 Published 2022-04-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
A potential vulnerability due to improper buffer validation in the SMI handler LenovoFlashDeviceInterface in Thinkpad X1 Fold Gen 1 could be exploited by an attacker with local access and 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 confidence

Improper buffer validation in the SMI (System Management Interface) handler named LenovoFlashDeviceInterface in ThinkPad X1 Fold Gen 1 firmware allows a local attacker with elevated privileges to execute arbitrary code. This is a firmware-level vulnerability in the BIOS/UEFI layer.

MitigationApply the Lenovo firmware update for ThinkPad X1 Fold Gen 1. Organizations should inventory affected systems, test the update in a controlled environment, and deploy via standard patch management processes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Thinkpad X1 Fold Gen 1 FirmwareOperating system
Affected:< n2pet50w

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm system model is ThinkPad X1 Fold Gen 1
    Run 'wmic computersystem get model' or check the system label/marketing name
    Affected if Model name does not contain 'ThinkPad X1 Fold Gen 1' or 'X1 Fold'
  2. Check installed BIOS/firmware version
    Boot into BIOS setup (press F1 or Enter at Lenovo logo) and view the BIOS version, or run 'wmic bios get smbiosbiosversion' from Windows command prompt, or use Lenovo Vantage/System Update to view firmware version
    Affected if Unable to retrieve firmware version information
  3. Compare firmware version against vulnerable range
    Compare the installed BIOS version string to the vulnerable version threshold: versions below n2pet50w are affected
    Affected if Installed firmware version is lexicographically or numerically less than 'n2pet50w'
  4. Verify SMI handler is accessible (optional deeper check)
    This requires low-level system tools or Lenovos diagnostic tools to inspect the SMI handler named LenovoFlashDeviceInterface; not accessible through standard OS utilities
    Affected if Standard users cannot directly verify SMI handler status - this check is for advanced forensic analysis only

A ThinkPad X1 Fold Gen 1 system with BIOS firmware version lower than n2pet50w is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Lenovo firmware update for ThinkPad X1 Fold Gen 1. Organizations should inventory affected systems, test the update in a controlled environment, and deploy via standard patch management processes.

Recommended fix Moderate confidence

Thinkpad X1 Fold Gen 1 Firmware n2pet50w or later

  1. 1. Visit the Lenovo support website (support.lenovo.com) and search for Thinkpad X1 Fold Gen 1 firmware updates
  2. 2. Download the firmware version n2pet50w or later
  3. 3. Follow Lenovo's standard firmware update procedure for the Thinkpad X1 Fold Gen 1, typically involving running the update utility with administrator privileges
  4. 4. Ensure the device is connected to power during the firmware update process
  5. 5. Restart the system after the firmware update completes
Caveat Firmware updates carry inherent risk; ensure backup of critical data and stable power connection during the update process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thinkpad X1 Fold Gen 1 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1108 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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