CVE-2022-1107
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 · uneditedDuring an internal product security audit a potential vulnerability due to use of Boot Services in the SmmOEMInt15 SMI handler was discovered in some ThinkPad models could be exploited by an attacker with elevated privileges that could allow for execution of 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 confidenceVulnerability in the SmmOEMInt15 SMI (System Management Mode interrupt) handler in ThinkPad firmware allows code execution via abuse of Boot Services within SMM context. The handler incorrectly uses Boot Services after they should have been terminated, creating a use-after-free type condition exploitable by an attacker with elevated privileges.
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< n15et78w< n17eta8w< n1het85w< n1xet65w< n1ket46w< n1vet50w< n27et36w< gpet80wwCVSS 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 modelRun 'systeminfo' on Windows or 'dmidecode -s system-product-name' on Linux, or physically inspect the laptop chassis or BIOS for the model numberAffected if Model is any of: ThinkPad 11e, ThinkPad Helix, ThinkPad L560, ThinkPad L570, ThinkPad P50s, ThinkPad P51s, ThinkPad P52s, ThinkPad S540
-
Check BIOS firmware versionRun 'systeminfo | findstr BIOS' on Windows or 'dmidecode -s bios-version' on Linux, or use Lenovo Vantage/System Update utility to view BIOS versionAffected if Firmware version is lower than the safe version for your model: ThinkPad 11e < n15et78w, ThinkPad Helix < n17eta8w, ThinkPad L560 < n1het85w, ThinkPad L570 < n1xet65w, ThinkPad P50s < n1ket46w, ThinkPad P51s < n1vet50w, ThinkPad P52s < n27et36w, ThinkPad S540 < gpet80ww
-
Confirm SmmOEMInt15 handler availabilityThis SMI handler is present in the firmware baseline. Detection requires vendor tooling or consulting the Lenovo vulnerability advisory for specific firmware build identifiers that contain the fixAffected if Your current BIOS build does not include the vendor patch addressing the SmmOEMInt15 use-after-free
You are affected if your ThinkPad model matches one of the eight listed models AND your installed BIOS/firmware version is below the version threshold specified 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 · scopedApply vendor-provided BIOS/firmware updates for affected ThinkPad models. Prioritize systems with elevated-privilege exposure or direct physical access.
Firmware version n15et78w (ThinkPad 11e), n17eta8w (ThinkPad Helix), n1het85w (ThinkPad L560), n1xet65w (ThinkPad L570), n1ket46w (ThinkPad P50s), n1vet50w (ThinkPad P51s), n27et36w (ThinkPad P52s), or gpet80ww (ThinkPad S540) - or any subsequent version
- 1. Identify the ThinkPad model number from the affected list (11e, Helix, L560, L570, P50s, P51s, P52s, or S540)
- 2. Determine the current firmware version installed on the device
- 3. Navigate to the Lenovo support website (support.lenovo.com) and locate the drivers and firmware section for the specific ThinkPad model
- 4. Download the firmware update that matches or exceeds the fixed version for the model: n15et78w for 11e, n17eta8w for Helix, n1het85w for L560, n1xet65w for L570, n1ket46w for P50s, n1vet50w for P51s, n27et36w for P52s, gpet80ww for S540
- 5. Follow Lenovo's firmware update instructions, which typically involve running the update utility with administrator privileges
- 6. Restart the system after the firmware update completes
- 7. Verify the firmware version has been successfully updated to the fixed version or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1107 — 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-1107 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