Dell BIOS contains a heap buffer overflow vulnerability.

published 2023-02-01 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-37355

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits: 0; none known

Dell BIOS contains a heap buffer overflow vulnerability. A local attacker with admin privileges could potentially exploit this vulnerability to perform an arbitrary write to SMRAM during SMM.

Patch / fix

fixed in 20

dell alienware_m15_r6_firmware 1.17.0
dell alienware_m15_r7_firmware 1.4.3
dell alienware_m15_ryzen_edition_r5_firmware 1.8.0
dell alienware_m17_r5_amd_firmware 1.4.3
dell g15_5510_firmware 1.16.0
dell g15_5511_firmware 1.18.0
dell g15_5515_firmware 1.8.0
dell g15_5525_firmware 1.4.3
dell g5_se_5505_firmware 1.13.0
dell inspiron_14_5410_2-in-1_firmware 2.15.2
dell inspiron_15_3511_firmware 1.18.2
dell inspiron_3195_2-in-1_firmware 1.6.0
dell inspiron_3275_firmware 1.9.2
dell inspiron_3475_firmware 1.9.2
dell inspiron_3505_firmware 1.9.0
dell inspiron_3515_firmware 1.9.0
dell inspiron_3525_firmware 1.5.0
dell inspiron_3585_firmware 1.10.0
dell inspiron_3595_firmware 1.5.0
dell inspiron_3785_firmware 1.10.0

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 19 mo ago (2025-03-27)

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD	3.1	7.1	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Affected products

Dell CPG BIOS

Classification

Weakness

CWE-122 Heap-based Buffer Overflow
CWE-787 Out-of-bounds Write

References

dell.com /support/kbdoc/en-us/000205716/dsa-2022-327
vendor-advisory

Sources

CVE List CVE-2022-34400
NVD CVE-2022-34400

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary