In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash.
In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. While this provides sufficient protection, an additional layer of protection is provided by SPI Protected Range Registers (PRx). After resuming from S3 sleep mode in various versions of BIOS for some Lenovo ThinkPad systems, the PRx is not set. This does not impact the SMM BIOS Write Protection, which keeps systems protected.
- Published
- Sep 1, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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 | thinkpad t490 \(20nx\) firmware | cpe:2.3:o:lenovo:thinkpad_t490_\(20nx\)_firmware |
| lenovo | thinkpad t490 \(20nx\) | cpe:2.3:h:lenovo:thinkpad_t490_\(20nx\) |
| lenovo | thinkpad t490 \(20qx\) firmware | cpe:2.3:o:lenovo:thinkpad_t490_\(20qx\)_firmware |
| lenovo | thinkpad t490 \(20qx\) | cpe:2.3:h:lenovo:thinkpad_t490_\(20qx\) |
| lenovo | thinkpad t490 \(20rx\) firmware | cpe:2.3:o:lenovo:thinkpad_t490_\(20rx\)_firmware |
| lenovo | thinkpad t490 \(20rx\) | cpe:2.3:h:lenovo:thinkpad_t490_\(20rx\) |
| lenovo | thinkpad t490s \(20nx\) firmware | cpe:2.3:o:lenovo:thinkpad_t490s_\(20nx\)_firmware |
| lenovo | thinkpad t490s \(20nx\) | cpe:2.3:h:lenovo:thinkpad_t490s_\(20nx\) |
| lenovo | thinkpad t495 drift firmware | cpe:2.3:o:lenovo:thinkpad_t495_drift_firmware |
| lenovo | thinkpad t495 drift | cpe:2.3:h:lenovo:thinkpad_t495_drift |
| lenovo | thinkpad t590 \(20nx\) firmware | cpe:2.3:o:lenovo:thinkpad_t590_\(20nx\)_firmware |
| lenovo | thinkpad t590 \(20nx\) | cpe:2.3:h:lenovo:thinkpad_t590_\(20nx\) |
and 8 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo thinkpad t490 (20nx) firmwarebefore n2iet90w
- lenovo thinkpad t490 (20qx) firmwarebefore n2iet90w
- lenovo thinkpad t490 (20rx) firmwarebefore n2ret16w
- lenovo thinkpad t490s (20nx) firmwarebefore n2jet89w
- lenovo thinkpad t495 drift firmwarebefore 2020-08-30
- lenovo thinkpad t590 (20nx) firmwarebefore n2iet90w
- lenovo thinkpad x1 carbon (20qx) firmwarebefore n2het54w
- lenovo thinkpad x1 yoga (20qx) firmwarebefore n2het54w
- lenovo thinkpad x390 (20qx) firmwarebefore n2jet89w
- lenovo thinkpad x390 (20sx) firmwarebefore n2set18w
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.
No credits in the CNA record.
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
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.