Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local OS admin or root access
-
DeliveryCraft malicious SMI call from ring-0
-
ExploitTrigger out-of-bounds write in SMM handler
-
ExecutionOverwrite SMRAM code or function pointers
-
PersistExecute arbitrary code in System Management Mode
-
ImpactImplant 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
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
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
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.
Primary rating from Vendor (lenovo).
CVSS VectorVendor: lenovo
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Yoga Pro 7 15Iph11 Bios
View allOut-of-bounds write in Lenovo BIOS firmware across dozens of consumer and gaming laptop models enables a local privilege
Lenovo BIOS firmware across dozens of consumer and gaming laptop models - Legion, IdeaPad, Yoga, ThinkBook, LOQ, and V-s
SMM memory address disclosure in Lenovo laptop BIOS firmware exposes the location of protected System Management Mode (S
EUVD-2026-44981
GHSA-pwmv-8h46-f444
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB