dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-10238

MEDIUM · 6.7 CVSS v3.1 Published 2026-06-10
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
During an internal security assessment, a potential out-of-bounds write vulnerability was discovered in the BIOS of some ThinkPad products could allow a privileged local user to execute code in System Management Mode (SMM).

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

An out-of-bounds write vulnerability in the BIOS firmware of certain ThinkPad products could allow a privileged local user to execute arbitrary code in System Management Mode (SMM), which operates at the highest privilege level on x86 systems.

MitigationApply the vendor-supplied BIOS/firmware update from Lenovo for affected ThinkPad models and verify successful installation.

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

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. Identify ThinkPad model
    Run 'systeminfo' on Windows or check 'dmidecode -s system-product-name' on Linux to confirm the system is a Lenovo ThinkPad
    Affected if System is not a ThinkPad (this vulnerability affects only ThinkPad products)
  2. Check BIOS/firmware version on Windows
    Run 'wmic bios get smbiosbiosversion' or check 'System Information' > 'BIOS Version' in msinfo32
    Affected if Unable to retrieve BIOS version information
  3. Check BIOS/firmware version on Linux
    Run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version
    Affected if Unable to retrieve BIOS version information
  4. Verify SMM is accessible
    Confirm the system is x86-based and System Management Mode is operational (default state on x86 ThinkPads). On Linux, check 'cat /proc/booted_kernel' or verify SMM is not explicitly disabled in firmware settings.
    Affected if Non-x86 architecture or SMM has been disabled (vulnerability is in SMM code)
  5. Compare against Lenovo advisory
    Cross-reference your ThinkPad model number and BIOS version with Lenovo's official security advisory for CVE-2025-10238 to determine if your specific version falls within affected ranges
    Affected if Your BIOS version matches a version listed as affected in Lenovo's official CVE-2025-10238 advisory

A system is affected if it is a ThinkPad with a BIOS version that matches Lenovo's list of affected versions for CVE-2025-10238, and the system uses x86 SMM (standard on ThinkPad x86 systems).

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied BIOS/firmware update from Lenovo for affected ThinkPad models and verify successful installation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10238 — 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-2025-10238 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