CVE-2022-4574
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 · uneditedAn SMI handler input validation vulnerability in the BIOS of some ThinkPad models could allow 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 confidenceThis is an input validation vulnerability in System Management Interrupt (SMI) handlers within the BIOS firmware of ThinkPad systems. The flaw allows a local attacker with existing elevated privileges to bypass validation checks and execute arbitrary code at the firmware level, potentially achieving persistent code execution that survives operating system reinstallation.
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< 1.40< 1.45< 1.33< 1.51< 1.26< 1.37< 1.59< 1.30CVSS 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.
-
Identify ThinkPad modelOn Windows: open Command Prompt and run 'wmic computersystem get model' or check System Information. On Linux: run 'dmidecode -s system-product-name' or check /sys/class/dmi/id/product_nameAffected if The model matches any of the affected ThinkPad models: X13, X13 Yoga Gen 1/2, X13 Gen 2/3, or X1 Yoga 5th/6th/7th Gen
-
Determine BIOS firmware versionOn Windows: open Command Prompt and run 'wmic bios get smbiosbiosversion' or check in Lenovo Vantage under Device > Device Settings. On Linux: run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_versionAffected if A BIOS version number is returned that can be compared against the fixed versions
-
Compare version against affected rangesMatch your identified model and BIOS version against: X13 Yoga Gen 2 < 1.40, X13 Yoga Gen 1 < 1.45, X13 Gen 3 < 1.33, X13 Gen 2 < 1.51, X13 < 1.26, X1 Yoga 7th Gen < 1.37, X1 Yoga 6th Gen < 1.59, X1 Yoga 5th Gen < 1.30Affected if The installed BIOS version is lower than the corresponding fixed version for your ThinkPad model
A user is affected if they own one of the listed ThinkPad models and their BIOS firmware version is below the specified threshold for that model.
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 · scoped1.261.301.33
Apply the BIOS/firmware update provided by Lenovo for affected ThinkPad models. Since exploitation requires local access and elevated privileges, ensure strict access controls to physical hardware and limit privileged account usage.
Thinkpad X13 Yoga Gen 2: >= 1.40 | Thinkpad X13 Yoga Gen 1: >= 1.45 | Thinkpad X13 Gen 3: >= 1.33 | Thinkpad X13 Gen 2: >= 1.51 | Thinkpad X13: >= 1.26 | Thinkpad X1 Yoga 7th Gen: >= 1.37 | Thinkpad X1 Yoga 6th Gen: >= 1.59 | Thinkpad X1 Yoga 5th Gen: >= 1.30
- 1. Identify the exact ThinkPad model number (e.g., X13 Yoga Gen 2) - check the bottom of the laptop or system information
- 2. Visit support.lenovo.com and enter the model number to find the BIOS/firmware download page
- 3. Download the BIOS update utility for the specific model
- 4. Connect the laptop to AC power and ensure battery is sufficiently charged (>50%)
- 5. Run the BIOS update utility and follow the on-screen prompts - do not interrupt the update process
- 6. Allow the system to restart and complete the firmware flash - this may take several minutes
- 7. Verify the BIOS version has been updated by checking system information or the BIOS setup (press F1 or Enter during boot)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4574 — 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-2022-4574 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