CVE-2022-31226
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 · uneditedDell BIOS versions contain a Stack-based Buffer Overflow vulnerability. A local authenticated malicious user could potentially exploit this vulnerability by sending excess data to a function in order to gain arbitrary code execution on the system.
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 analysisData overflows a fixed-size buffer allocated on the stack, overwriting adjacent stack memory — including saved return addresses — which is the classic route to redirecting execution into attacker-supplied code. Crafted input is all it takes. Remediation is strict length checks, safe bounded string and memory functions, and modern stack-protection mitigations.
General guidance for the stack-based buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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.1.66< 1.2.0< 1.2.0< 1.1.66< 1.1.0< 1.4.1< 1.4.1< 1.3.0CVSS 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
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.1.01.1.661.2.0
BIOS firmware version 1.1.66 (Chengming 3900, Inspiron 3910), 1.2.0 (Inspiron 14 Plus 7420, Inspiron 16 Plus 7620), 1.1.0 (Inspiron 5320), 1.4.1 (Inspiron 5420, Inspiron 5620), or 1.3.0 (Inspiron 7420) depending on model
- Navigate to Dell support KB article 000202196 at https://www.dell.com/support/kbdoc/000202196
- Identify your exact Dell model from the affected products list (Chengming 3900, Inspiron 14 Plus 7420, Inspiron 16 Plus 7620, Inspiron 3910, Inspiron 5320, Inspiron 5420, Inspiron 5620, or Inspiron 7420)
- Download the BIOS update utility corresponding to your specific model and current firmware version
- Run the Dell BIOS update executable while connected to AC power (do not run on battery only)
- Allow the update to complete - the system will restart and flash the new BIOS firmware
- Verify the BIOS version has been updated to the fixed release (1.1.66 for Chengming 3900/Inspiron 3910, 1.2.0 for Inspiron 14 Plus 7420/Inspiron 16 Plus 7620, 1.1.0 for Inspiron 5320, 1.4.1 for Inspiron 5420/Inspiron 5620, or 1.3.0 for Inspiron 7420)
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31226 — 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-31226 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