CVE-2023-43570
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 was reported in the SMI callback function of the OemSmi driver that may allow a local attacker with elevated permissions 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 a firmware-level vulnerability in the OemSmi UEFI driver's SMI (System Management Interrupt) callback function. The flaw allows a local attacker with elevated privileges to execute arbitrary code, likely through improper input validation or memory handling within the SMI handler. This represents a privilege escalation issue at the firmware layer.
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< o4hkt3ca< o4fkt39a< m2vkt21a< m42kt46a< m4ukt36aall versionsall versions< m40kt45aCVSS 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 system modelRun `dmidecode -s system-product-name` on Linux or `wmic baseboard get product,Manufacturer` on Windows to get the exact model numberAffected if The model matches one of: Ideacentre C5 14imb05, Ideacentre 3 07ada05, Ideacentre 3 07imb05, Ideacentre 5 14iab7, Ideacentre 5 14irb8, Ideacentre 5 14acn6, Ideacentre T540 15ama G, or Thinkcentre Neo 70t Gen 3
-
Check the UEFI/BIOS firmware versionRun `dmidecode -s bios-version` on Linux or `wmic bios get smbiosbiosversion` on Windows to retrieve the current firmware version stringAffected if The firmware version cannot be determined or is returned as unknown
-
Compare firmware version against affected ranges for Ideacentre C5 14imb05If system is Ideacentre C5 14imb05, compare your version to o4hkt3ca - any version below o4hkt3ca is affectedAffected if Installed version is less than o4hkt3ca (lexicographically or numerically)
-
Compare firmware version against affected ranges for Ideacentre 3 modelsIf system is Ideacentre 3 07ada05, compare to o4fkt39a; if Ideacentre 3 07imb05, compare to m2vkt21aAffected if Installed version is less than o4fkt39a (for 07ada05) or less than m2vkt21a (for 07imb05)
-
Compare firmware version against affected ranges for Ideacentre 5 modelsIf system is Ideacentre 5 14iab7, compare to m42kt46a; if 14irb8, compare to m4ukt36a; if 14acn6, all versions are affectedAffected if Installed version is less than m42kt46a (14iab7), less than m4ukt36a (14irb8), or any version (14acn6)
-
Compare firmware version for Thinkcentre Neo 70t Gen 3 and Ideacentre T540If system is Thinkcentre Neo 70t Gen 3, compare to m40kt45a; Ideacentre T540 15ama G has all versions affectedAffected if Installed version is less than m40kt45a (Neo 70t) or system is Ideacentre T540 15ama G
The system is affected if it is any of the listed Lenovo models AND its firmware version falls below the specified threshold, or if it is Ideacentre 5 14acn6 or Ideacentre T540 15ama G at any version.
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 vendor-provided BIOS/firmware update that patches the OemSmi driver. Until the patch is available, limit physical and administrative access to affected systems and monitor for signs of firmware tampering.
Firmware version >= o4hkt3ca (C5 14imb05), >= o4fkt39a (3 07ada05), >= m2vkt21a (3 07imb05), >= m42kt46a (5 14iab7), >= m4ukt36a (5 14irb8), >= m40kt45a (Thinkcentre Neo 70t Gen 3), or latest available for 14acn6 and T540 15ama G
- 1. Identify the exact model number of your Lenovo system (Ideacentre or Thinkcentre)
- 2. Navigate to Lenovo's support website at support.lenovo.com
- 3. Enter your specific model number to access the product support page
- 4. Locate the 'Driver & Downloads' or 'BIOS/Firmware' section
- 5. Download the firmware version equal to or higher than the fixed version for your model: o4hkt3ca for C5 14imb05, o4fkt39a for 3 07ada05, m2vkt21a for 3 07imb05, m42kt46a for 5 14iab7, m4ukt36a for 5 14irb8, m40kt45a for Thinkcentre Neo 70t Gen 3
- 6. For Ideacentre 5 14acn6 and Ideacentre T540 15ama G (all versions affected), download the latest available firmware version from Lenovo support
- 7. Follow Lenovo's firmware update instructions, which typically require running the update utility from Windows or creating a bootable USB update disk
- 8. Ensure the system maintains power during the firmware update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43570 — 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-2023-43570 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