Skip to content
Noroxi
CVE-2022-4574· NVD / CVE Program· CNA lenovo

An SMI handler input validation vulnerability in the BIOS of some ThinkPad models could allow an attacker with local access and elevated pr

An SMI handler input validation vulnerability in the BIOS of some ThinkPad models could allow an attacker with local access and elevated privileges to execute arbitrary code.  

MediumCVSS 6.7 · v3.1—No exploit No fix recorded
Published
Oct 30, 2023
Updated
Jun 17, 2026
EPSS
0.2% · 8th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

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 help

Affected systems

VendorProduct
lenovothinkpad x13 yoga gen 2 firmware
lenovothinkpad x13 yoga gen 2
lenovothinkpad x13 yoga gen 1 firmware
lenovothinkpad x13 yoga gen 1
lenovothinkpad x13 gen 3 firmware
lenovothinkpad x13 gen 3
lenovothinkpad x13 gen 2 firmware
lenovothinkpad x13 gen 2
lenovothinkpad x13 firmware
lenovothinkpad x13
lenovothinkpad x1 yoga 7th gen firmware
lenovothinkpad x1 yoga 7th gen

and 96 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lenovo thinkpad l14 firmwarebefore 1.20
  • lenovo thinkpad l14 gen 2 firmwareall versions
  • lenovo thinkpad l15 firmwarebefore 1.20
  • lenovo thinkpad l15 gen 2 firmwareall versions
  • lenovo thinkpad p1 gen 3 firmwarebefore 1.27
  • lenovo thinkpad p1 gen 4 firmware1.22
  • lenovo thinkpad p1 gen 5 firmwarebefore 1.16
  • lenovo thinkpad p14s gen 1 firmwarebefore 1.28
  • lenovo thinkpad p14s gen 2 firmwareall versions
  • lenovo thinkpad p14s gen 3 firmwarebefore 1.31
  • lenovo thinkpad p15 gen 1 firmwarebefore 1.32
  • lenovo thinkpad p15 gen 2 firmwarebefore 1.25
  • lenovo thinkpad p15s gen 1 firmwarebefore 1.28
  • lenovo thinkpad p15s gen 2 firmwareall versions
  • lenovo thinkpad p15v gen 1 firmwarebefore 1.32
  • lenovo thinkpad p15v gen 2 firmwarebefore 1.19
  • lenovo thinkpad p15v gen 3 firmwarebefore 1.15
  • lenovo thinkpad p16 gen 1 firmwarebefore 1.17
  • lenovo thinkpad p16s gen 1 firmwarebefore 1.31
  • lenovo thinkpad p17 gen 1 firmwarebefore 1.32

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 BIOS

    • 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.

EPSS, last 120 days

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 researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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-20 · Improper Input Validation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

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.

All records