CVE-2021-3719
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 vulnerability in the SMI callback function that saves and restore boot script tables used for resuming from sleep state in some ThinkCentre and ThinkStation models may 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 · high confidenceA vulnerability exists in the SMI (System Management Interface) callback function responsible for saving and restoring boot script tables during sleep/resume operations on certain Lenovo ThinkCentre and ThinkStation systems. This allows a local attacker with already elevated privileges to execute arbitrary code via the firmware-level attack vector.
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< fbktdfa< m00kt65a< fwktb9a< fhkt86a< fbktdfa< fwktb9a< m1ekt23a< fbktdfaCVSS 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 the ThinkCentre model numberCheck the system label on the chassis or run 'wmic csproduct get name' or check BIOS information via 'dmidecode -s system-product-name'Affected if The model is one of: E93, M600, M700 Tiny, M73, M73p, M800, M818z, or M83
-
Determine the installed BIOS/firmware versionEnter BIOS setup (F1 on boot) or run 'wmic bios get smbiosbiosversion' or use 'dmidecode -s bios-version'Affected if The firmware version is lower than the threshold for your model (E93: fbktdfa, M600: m00kt65a, M700 Tiny: fwktb9a, M73: fhkt86a, M73p: fbktdfa, M800: fwktb9a, M818z: m1ekt23a, M83: fbktdfa)
-
Verify sleep/resume functionality is configuredCheck power management settings in Windows Power Options or Linux /sys/power/state, or verify S3 sleep state is enabled in BIOSAffected if Sleep/resume (S3 state) is enabled - this is required for the vulnerable SMI callback to be invoked during the sleep/resume cycle
You are affected if your ThinkCentre model matches one of the listed variants AND your current firmware version is lower than the specified threshold, regardless of sleep/resume configuration since the vulnerable code exists in firmware regardless of whether the feature is actively used.
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 the Lenovo firmware update corresponding to your model from the official Lenovo support portal; this is a BIOS/UEFI firmware vulnerability requiring system firmware remediation rather than software patching.
ThinkCentre firmware version fbktdfa (E93/M73p/M83), m00kt65a (M600), fwktb9a (M700 Tiny/M800), fhkt86a (M73), or m1ekt23a (M818z) or later depending on model
- Identify the exact ThinkCentre model number from the affected list (E93, M600, M700 Tiny, M73, M73p, M800, M818z, or M83)
- Visit the official Lenovo support website at support.lenovo.com
- Enter the specific model number in the search or product lookup field
- Navigate to the Drivers & Software or BIOS/Firmware section
- Locate the BIOS/firmware update for the system
- Verify the version number meets or exceeds the fixed version for your model: E93/M73p/M83: fbktdfa or higher, M600: m00kt65a or higher, M700 Tiny/M800: fwktb9a or higher, M73: fhkt86a or higher, M818z: m1ekt23a or higher
- Download the firmware update package
- Review any pre-update requirements in the release notes (e.g., connected to AC power, battery charged)
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-2021-3719 — 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-2021-3719 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