CVE-2022-26864
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 · uneditedPrior Dell BIOS versions contain an Input Validation vulnerability. A locally authenticated malicious user could potentially exploit this vulnerability by sending malicious input to an SMI in order to bypass security controls in SMM.
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 confidenceThis is an input validation vulnerability in prior Dell BIOS versions that allows a locally authenticated malicious user to send malicious input to the System Management Interface (SMI), potentially bypassing security controls in System Management Mode (SMM). SMM is a high-privilege CPU mode that operates below the operating system, making this a serious privilege escalation issue.
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< 1.5.0< 1.6.0< 1.11.0< 2.16.1< 1.2.1< 1.9.0< 1.9.0< 1.4.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the exact Dell system modelRun 'dmidecode -s system-product-name' on Linux or check System Information on Windows to confirm the exact model number (e.g., Alienware M15 R5, G15 5515, etc.)Affected if The system model matches one of the listed affected products: Alienware M15 R5, G15 5515, G5 Se 5505, Inspiron 27 7775, Inspiron 14 5425, Inspiron 3275, Inspiron 3475, or Inspiron 3180
-
Determine the current BIOS firmware versionRun 'dmidecode -s bios-version' on Linux, 'wmic bios get smbiosbiosversion' on Windows, or check the BIOS/UEFI setup screen during bootAffected if The installed BIOS version is lower than the threshold for your model (1.5.0 for Alienware M15 R5, 1.6.0 for G15 5515, 1.11.0 for G5 Se 5505, 2.16.1 for Inspiron 27 7775, 1.2.1 for Inspiron 14 5425, 1.9.0 for Inspiron 3275/3475, or 1.4.4 for Inspiron 3180)
-
Verify the System Management Interface is accessibleThis is a BIOS-level component present on affected systems; confirm the system has SMM capability by checking 'dmidecode' output for SMBIOS or reviewing system specificationsAffected if The system uses Dell firmware with System Management Interface (SMI) support, which is standard on the listed affected models
A system is affected if it is one of the listed Dell models AND its current BIOS firmware version is below the specified version threshold for that model.
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.
dbcve · scoped1.2.11.4.41.5.0
Update Dell BIOS to the latest vendor-provided version that addresses this vulnerability. Organizations should identify affected systems using Dell's support tools and deploy the BIOS update through their standard firmware management processes, preferably using encrypted update mechanisms.
BIOS firmware updated to version 1.5.0 (Alienware M15 R5), 1.6.0 (G15 5515), 1.11.0 (G5 Se 5505), 2.16.1 (Inspiron 27 7775), 1.2.1 (Inspiron 14 5425), 1.9.0 (Inspiron 3275/3475), or 1.4.4 (Inspiron 3180) as applicable
- Identify the exact Dell system model number (e.g., Alienware M15 R5, G15 5515, etc.)
- Navigate to Dell Support website (www.dell.com) and enter the service tag or search for the product model
- Locate the 'BIOS' section under Drivers & Downloads
- Download the BIOS update file corresponding to the fixed version: Alienware M15 R5 to version 1.5.0 or later; G15 5515 to version 1.6.0 or later; G5 Se 5505 to version 1.11.0 or later; Inspiron 27 7775 to version 2.16.1 or later; Inspiron 14 5425 to version 1.2.1 or later; Inspiron 3275 to version 1.9.0 or later; Inspiron 3475 to version 1.9.0 or later; Inspiron 3180 to version 1.4.4 or later
- Ensure the system is connected to AC power and not battery only
- Run the downloaded BIOS update executable or extract and run from within Windows/UEFI environment
- Follow the on-screen prompts and allow the system to restart for the BIOS flash process
- Do not interrupt power or shut down during the BIOS update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26864 — 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-2022-26864 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