CVE-2019-6190
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLenovo was notified of a potential denial of service vulnerability, affecting various versions of BIOS for Lenovo Desktop, Desktop - All in One, and ThinkStation, that could cause PCRs to be cleared intermittently after resuming from sleep (S3) on systems with Intel TXT enabled.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLenovo BIOS vulnerability allows PCRs (Platform Configuration Registers) to be cleared intermittently after resuming from S3 sleep on systems with Intel TXT (Trusted Execution Technology) enabled, potentially causing denial of service due to failed integrity measurements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< fbktdba< fbktdba< fbktdba< fbktdba< fbktdba< fbktdba< fbktdba< fbktdbaCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your ThinkCentre modelCheck the system model via the System Information utility, command line (dmidecode -s system-product-name), or the physical system label.Affected if The model is one of: E93, M6500s, M6500t, M73p, M83, M8500s, M8500t, or M93.
-
Check BIOS firmware versionAccess the BIOS setup (press F1 or Delete at startup) and locate the BIOS version information, or use the command 'dmidecode -s bios-version' on Linux systems, or run Lenovo System Update / Lenovo Vantage to query the firmware.Affected if The installed BIOS firmware version is lower than fbktdba (for example, an earlier version number).
-
Verify Intel TXT statusEnter the BIOS/UEFI setup (F1 or Delete at boot) and navigate to the Security or Advanced menu to locate the Intel Trusted Execution Technology (TXT) setting. If available from the operating system, tools like 'txt-stat' on Linux can report TXT status.Affected if Intel TXT is enabled in the BIOS configuration.
-
Check for S3 sleep resume behaviorObserve system behavior after resuming from S3 sleep (suspend to RAM). Look for boot failures, integrity measurement errors, or unexpected reboots that may indicate PCR values were cleared.Affected if The system exhibits boot failures or integrity errors specifically after waking from S3 sleep, especially with Intel TXT enabled.
You are affected if you own one of the listed ThinkCentre models, your BIOS version is below fbktdba, and Intel TXT is enabled in the BIOS settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the BIOS update provided by Lenovo for affected Desktop, Desktop - All in One, and ThinkStation systems. If unable to update immediately, consider disabling Intel TXT as a workaround, though this reduces system security protections.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6190 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data