A potential vulnerability in the SMI callback function used in the Legacy USB driver in some Lenovo Notebook and ThinkStation models may all
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- 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.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A potential vulnerability in the SMI callback function used in the Legacy USB driver in some Lenovo Notebook and ThinkStation models may allow arbitrary code execution.
- Published
- Jun 9, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- —
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.3%
CNA vs NVD score
- NVD
- 6.7
- CNA · lenovo
- 6.4
- 0.3 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lenovo | 330-14ast firmware | cpe:2.3:o:lenovo:330-14ast_firmware |
| lenovo | 330-14ast | cpe:2.3:h:lenovo:330-14ast |
| lenovo | 330-15ast firmware | cpe:2.3:o:lenovo:330-15ast_firmware |
| lenovo | 330-15ast | cpe:2.3:h:lenovo:330-15ast |
| lenovo | 330-17ast firmware | cpe:2.3:o:lenovo:330-17ast_firmware |
| lenovo | 330-17ast | cpe:2.3:h:lenovo:330-17ast |
| lenovo | 340c-15api firmware | cpe:2.3:o:lenovo:340c-15api_firmware |
| lenovo | 340c-15api | cpe:2.3:h:lenovo:340c-15api |
| lenovo | 340c-15ast firmware | cpe:2.3:o:lenovo:340c-15ast_firmware |
| lenovo | 340c-15ast | cpe:2.3:h:lenovo:340c-15ast |
| lenovo | 720s touch-15ikb firmware | cpe:2.3:o:lenovo:720s_touch-15ikb_firmware |
| lenovo | 720s touch-15ikb | cpe:2.3:h:lenovo:720s_touch-15ikb |
and 90 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo 14iwl firmwareall versions
- lenovo 330-14ast firmwareall versions
- lenovo 330-15ast firmwareall versions
- lenovo 330-17ast firmwareall versions
- lenovo 340c-15api firmwareall versions
- lenovo 340c-15ast firmwareall versions
- lenovo 6 pro-13-iwl firmwareall versions
- lenovo 6 pro-14-iwl firmwareall versions
- lenovo 720s touch-15ikb firmwareall versions
- lenovo 720s-15ikb firmwareall versions
- lenovo 730s-13iwl firmwareall versions
- lenovo c640-iml firmwareall versions
- lenovo e42-80 firmwareall versions
- lenovo e52-80 firmwareall versions
- lenovo e53-80 firmwareall versions
- lenovo k22-80 firmwareall versions
- lenovo k3 firmwareall versions
- lenovo k32-80 kbl firmwareall versions
- lenovo k32-80 skl firmwareall versions
- lenovo k4-iwl firmwareall versions
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 BIOS
- variousaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-8323A potential vulnerability in the SMI callback function used in the Legacy SD driver in some Lenovo ThinkPad, ThinkStation, and Lenovo Notebo26Monitor
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.
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)
—
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.
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.