Skip to main content

Lenovo BIOS Firmware EUVDEUVD-2026-44981

| CVE-2026-10589 MEDIUM
Out-of-bounds Write (CWE-787)
2026-07-16 lenovo GHSA-pwmv-8h46-f444
6.8
CVSS 4.0 · Vendor: lenovo
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local OS admin or root access
  2. Delivery
    Craft malicious SMI call from ring-0
  3. Exploit
    Trigger out-of-bounds write in SMM handler
  4. Execution
    Overwrite SMRAM code or function pointers
  5. Persist
    Execute arbitrary code in System Management Mode
  6. Impact
    Implant persistent firmware-level rootkit

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to have achieved local OS-level administrator (Windows) or root (Linux) privileges on an affected Lenovo device running unpatched BIOS firmware - confirming CVSS PR:H. The attack is delivered by executing privileged ring-0 code capable of issuing SMI calls or manipulating SMM-visible data structures, which is only accessible from an already-elevated OS context. Unprivileged local users and remote attackers without prior local code execution capability cannot trigger this vulnerability. Exploitation is constrained to the specific hardware models listed in the CPE data; unaffected Lenovo models or non-Lenovo hardware are not impacted. Secure Boot is not a limiting factor, as SMM operates beneath the Secure Boot enforcement layer. No non-default configuration setting is required - the flaw exists in the BIOS firmware as shipped on affected hardware.

Impact

Lenovo's CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N) scores 6.8 and reflects local exploitation requiring high OS-level privileges with low complexity. This score likely understates real-world severity: SMM code execution intrinsically grants read/write access to all system memory including OS kernel and hypervisor memory, making VC:N inconsistent with actual SMM semantics - confidentiality impact is inferred to exist even if not reflected in Lenovo's conservative CVSS assignment. The SC:N/SI:N/SA:N (no subsequent-system impact) is also arguably inconsistent with SMM's capability to modify firmware, persist across OS reinstalls, and undermine platform trust. No EPSS data was provided, and there is no CISA KEV listing or public exploit code at time of analysis. The high-privilege prerequisite (PR:H) significantly limits opportunistic exploitation; however, in targeted intrusions against high-value individuals (executives, government, defense), an adversary who already holds OS admin access could leverage this flaw for persistence that defeats standard incident response. The absence of POC and KEV listing suggests this is not currently being mass-exploited but remains a priority for environments with elevated threat models.

Exploit ScenarioDerived

A threat actor who has already achieved OS administrator or root-level access on an affected Lenovo laptop crafts a malicious SMI (System Management Interrupt) call or manipulates data structures inspected by the vulnerable SMM handler, triggering an out-of-bounds write that overwrites code or function pointers within SMRAM. This redirects SMM execution to attacker-controlled shellcode running at a privilege level below the OS kernel, from which the attacker can read all system memory, modify UEFI firmware variables, or implant a firmware rootkit that persists through OS reinstallation and evades endpoint detection tools. No public exploit code has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 16, 2026

Out-of-bounds write in Lenovo BIOS firmware across dozens of consumer and gaming laptop models enables a local attacker with high OS-level privileges to execute arbitrary code in System Management Mode (SMM) - a CPU execution context operating below the operating system and hypervisor with access to all system memory. Successful exploitation allows persistent firmware-level implants that survive OS reinstallation and defeat Secure Boot and standard endpoint detection tools. No public exploit has been identified at time of analysis, and this vulnerability is not listed in CISA KEV; however, SMM code execution represents one of the highest-impact firmware attack primitives available to an advanced threat actor.

RemediationAI

The primary remediation is to apply the BIOS firmware update released by Lenovo for each affected model. Consult the vendor security advisory at https://support.lenovo.com/us/en/product_security/LEN-220440 for the specific patched firmware version number applicable to each device, as version numbers differ per model. Updates can be applied via Lenovo Vantage (Windows), the Lenovo System Update utility, or manual BIOS flashing from the Lenovo support site; always perform firmware updates on AC power with a charged battery to avoid bricking the device during flash. Exact patched firmware version numbers are not independently verified from the available data - the advisory must be consulted for this. As a compensating control where immediate firmware patching is not feasible, enforce strict least-privilege policies to prevent unauthorized users from gaining OS-level admin or root access, since PR:H is required for exploitation; note this does not eliminate risk if an adversary already holds admin privileges through another means. Disabling or restricting SMI-invoking pathways at the OS level is generally not feasible without disrupting legitimate firmware functions. Secure Boot does not mitigate this vulnerability, as SMM operates below the Secure Boot enforcement boundary.

Affected VersionsENISA

Lenovo S14 G3 IAP BIOS 0 ≤JKCN49WW
Legion 5 15AKP10 BIOS 0 ≤RYCN22WW
Legion 9 16IRX9 BIOS 0 ≤NXCN20WW
Lenovo V15 G4 IAH BIOS 0 <MCCN39WW
Legion Pro 7 16IAX10H BIOS 0 ≤Q7CN31WW
Legion 5 15AHP10 BIOS 0 <RGCN35WW
IdeaPad Slim 3 15AMN8 BIOS 0 <L1CN51WW
LOQ 15IAX9E BIOS 0 ≤Q8CN17WW
IdeaPad Pro 5 16IRH8 BIOS 0 ≤KZCN46WW
Legion Pro 7 16ARX8H BIOS 0 ≤LPCN45WW
IdeaPad Slim 3 16IRH10R BIOS 0 ≤QDCN23WW
ThinkBook 16p G5 IRX BIOS 0 <P5CN31WW
IdeaPad Pro 5 16IMH9 BIOS 0 ≤MECN68WW
Lenovo V14 G6 ITN BIOS 0 <RHCN20WW
Yoga Book 9 14IAH10 BIOS 0 ≤QEME23WW
ThinkBook Plus G4 IRU BIOS 0 ≤LUCN47WW
IdeaPad Slim 3 16IRH8 BIOS 0 <LTCN44WW
Legion Pro 7 16ADR10H BIOS 0 <SJCN17WW
IdeaPad Pro 5 16IAH10 BIOS 0 ≤PZCN27WW
Legion Pro 7 16ARX8H BIOS 0 ≤LPCN59WW
Yoga Pro 9 16IMH9 BIOS 0 ≤NKCN30WW
Yoga Book 9 13IMU9 BIOS 0 ≤NVCN24WW
LOQ 15ARP10E BIOS 0 <SUCN18WW
IdeaPad Slim 3 16ARP10 BIOS 0 <QBCN30WW
Lenovo V15 G6 ARP BIOS 0 ≤TYCN15WW
ThinkBook 16p G6 ADR BIOS 0 <R7CN26WW
ThinkBook Plus G6 Rollable BIOS 0 ≤QWCN34WW
IdeaPad Slim 3 14ITN9 BIOS 0 <QUCN20WW
Lenovo V15 G4 AMN BIOS 0 <L1CN72WW
Yoga Pro 9 14IRP8 BIOS 0 ≤MBCN33WW
Lenovo V15 G2 IJL Laptop BIOS 0 <HTCN49WW
Legion 7 16IAX10 BIOS 0 ≤RXCN18WW
Legion 5 15APH9 BIOS 0 <PJCN18WW
Legion 5 15IAX10 BIOS 0 ≤S2CN15WW
Legion Pro 5 16IRX9 BIOS 0 <N0CN35WW
IdeaPad Pro 5 16AGP11 BIOS 0 ≤T8CN19WW
Legion Slim 5 14APH8 BIOS 0 ≤MACN33WW
ThinkBook 16p G6 IAX BIOS 0 <R2CN57WW
Legion Pro 5 16IRX10 BIOS 0 ≤S9CN13WW
Yoga 9 14IRP8 BIOS 0 <L4CN31WW
ThinkBook Plus G5 Tab&ThinkBook Plus G5 Station BIOS 0 ≤P8CN42WW
Lenovo V15 G5 IRL BIOS 0 <PMCN38WW
Legion Pro 5 16ARX8 BIOS 0 ≤LPCN59WW
Legion Pro 5 16AFR10 BIOS 0 ≤RECN14WW
Legion 5 15IRX9 BIOS 0 ≤PTCN14WW
Legion Pro 5 16ADR10 BIOS 0 ≤U5CN07WW
Legion 7 16AGP11 BIOS 0 ≤TPCN27WW
Yoga Book 9 14IAH10 BIOS 0 ≤QECN21WW
IdeaPad 5 15ABA7 BIOS 0 <KACN29WW
Yoga 9 2-in-1 14ILL10 BIOS 0 ≤Q9CN22WW
Yoga Pro 7 15IPH11 BIOS 0 <TNCN37WW
Legion Pro 7 16AFR10H BIOS 0 <SMCN20WW
Legion 5 15IRX10 BIOS 0 ≤QNCN28WW
IdeaPad Pro 5 16ASP10 BIOS 0 ≤R1CN24WW
Legion Pro 7 16IRX9H BIOS 0 ≤N2CN26WW
IdeaPad Slim 3 16IRU9 BIOS 0 <P2CN27WW
Yoga 9 2-in-1 14IMH9 BIOS 0 ≤NNCN31WW
Legion Pro 5 16ADR10 BIOS 0 ≤RLCN21WW
IdeaPad Pro 5 16IPH11 BIOS 0 <S4CN62WW
Legion Pro 5 16IAX10 BIOS 0 ≤Q6CN26WW

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

System Management Mode (SMM) is a special-purpose x86/x86-64 CPU execution mode used by UEFI firmware for low-level hardware management, power control, and OEM-specific functionality. SMM code runs in System Management RAM (SMRAM), a protected memory region that is intended to be inaccessible from the OS, hypervisor, and even ring-0 kernel code. The vulnerability is an out-of-bounds write (consistent with CWE-787, though CWE is listed N/A; vendor tags classify it as a buffer overflow) in one or more SMM handlers - code that processes System Management Interrupts (SMIs) from the OS layer. A write operation in this handler can exceed its intended buffer boundary, overwriting adjacent memory in or near SMRAM, ultimately allowing attacker-controlled data to redirect SMM execution flow. Per CPE data, affected products span both Intel-platform models (IPH, IRH, IAH, IRX, IAX, IRP, IMH suffixes) and AMD-platform models (AGP, ARP, AKP, AFR suffixes), covering IdeaPad, Yoga, Legion, ThinkBook, LOQ, and Lenovo V-series product lines.

Know when Yoga Pro 7 15Iph11 Bios gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (lenovo) PRIMARY 6.8 MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.2 HIGH

SMM execution crosses the OS security scope boundary (S:C); from SMM, all system memory is readable and writable, yielding C:H/I:H/A:H despite Lenovo's conservative VC:N.

3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (lenovo).

CVSS VectorVendor: lenovo

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A potential out of bounds write vulnerability could allow a local privileged attacker to execute code in System Management Mode.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
popular consumer and gaming laptop lines, not enterprise-ubiquitous infrastructure
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy