A buffer overflow has been identified in the BoardUpdateAcpiDxe driver in some Lenovo ThinkPad products which may allow an attacker with loc
A buffer overflow has been identified in the BoardUpdateAcpiDxe driver in some Lenovo ThinkPad products which may allow an attacker with local access and elevated privileges to execute arbitrary code.
- Published
- Aug 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 8th percentile
- CWE
- CWE-120
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.7
- CNA · lenovo
- 6.7
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| lenovo | k14 type 21cu firmware | cpe:2.3:o:lenovo:k14_type_21cu_firmware |
| lenovo | k14 type 21cu | cpe:2.3:h:lenovo:k14_type_21cu |
| lenovo | k14 type 21cv firmware | cpe:2.3:o:lenovo:k14_type_21cv_firmware |
| lenovo | k14 type 21cv | cpe:2.3:h:lenovo:k14_type_21cv |
| lenovo | thinkpad s2 yoga gen 8 firmware | cpe:2.3:o:lenovo:thinkpad_s2_yoga_gen_8_firmware |
| lenovo | thinkpad s2 yoga gen 8 | cpe:2.3:h:lenovo:thinkpad_s2_yoga_gen_8 |
| lenovo | thinkpad e14 gen 3 firmware | cpe:2.3:o:lenovo:thinkpad_e14_gen_3_firmware |
| lenovo | thinkpad e14 gen 3 | cpe:2.3:h:lenovo:thinkpad_e14_gen_3 |
| lenovo | thinkpad e15 gen 3 firmware | cpe:2.3:o:lenovo:thinkpad_e15_gen_3_firmware |
| lenovo | thinkpad e15 gen 3 | cpe:2.3:h:lenovo:thinkpad_e15_gen_3 |
| lenovo | thinkpad l13 gen 2 firmware | cpe:2.3:o:lenovo:thinkpad_l13_gen_2_firmware |
| lenovo | thinkpad l13 gen 2 | cpe:2.3:h:lenovo:thinkpad_l13_gen_2 |
and 40 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo k14 type 21cu firmwarebefore 1.12
- lenovo k14 type 21cv firmwarebefore 1.12
- lenovo thinkpad e14 gen 3 firmwarebefore 1.15
- lenovo thinkpad e15 gen 3 firmwarebefore 1.15
- lenovo thinkpad l13 gen 2 firmwarebefore 1.30
- lenovo thinkpad l13 gen 3 firmwarebefore 1.19
- lenovo thinkpad l13 gen 4 firmwarebefore 1.10
- lenovo thinkpad l13 yoga gen 2 firmwarebefore 1.30
- lenovo thinkpad l13 yoga gen 3 firmwarebefore 1.19
- lenovo thinkpad l13 yoga gen 4 firmwarebefore 1.10
- lenovo thinkpad l14 gen 2 firmwarebefore 1.28
- lenovo thinkpad l14 gen 3 firmwarebefore 1.23
- lenovo thinkpad l14 gen 4 firmwarebefore 1.06
- lenovo thinkpad l15 gen 2 firmwarebefore 1.28
- lenovo thinkpad l15 gen 3 firmwarebefore 1.23
- lenovo thinkpad l15 gen 4 firmwarebefore 1.06
- lenovo thinkpad p14s gen 2 firmwarebefore 1.34
- lenovo thinkpad s2 gen 6 firmwarebefore 1.30
- lenovo thinkpad s2 gen 7 firmwarebefore 1.19
- lenovo thinkpad s2 gen 8 firmwarebefore 1.10
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Lenovo ThinkPad
- variousaffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Zichuan Li (@Ri7erLi)Indiana University Bloomington for reporting this vulnerability.finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];if (pkt->len > sizeof(buf)) { return -EINVAL;}memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.