# CVE-2022-30426: Memory corruption in n/a

> A stack buffer overflow in Acer UEFI DXE drivers allows attackers to execute arbitrary code and escalate privileges from ring 3 to ring 0.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-gj8c-59qc-mfr6

## What is CVE-2022-30426?

CVE-2022-30426 is a high-severity memory corruption vulnerability in n/a, published on 22 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a stack buffer overflow vulnerability, which could lead to arbitrary code execution in UEFI DXE driver on some Acer products. An attack could exploit this vulnerability to escalate privilege from ring 3 to ring 0, and hijack control flow during UEFI DXE execution. This affects Altos T110 F3 firmware version <= P13 (latest) and AP130 F2 firmware version <= P04 (latest) and Aspire 1600X firmware version <= P11.A3L (latest) and Aspire 1602M firmware version <= P11.A3L (latest) and Aspire 7600U firmware version <= P11.A4 (latest) and Aspire MC605 firmware version <= P11.A4L (latest) and Aspire TC-105 firmware version <= P12.B0L (latest) and Aspire TC-120 firmware version <= P11-A4 (latest) and Aspire U5-620 firmware version <= P11.A1 (latest) and Aspire X1935 firmware version <= P11.A3L (latest) and Aspire X3475 firmware version <= P11.A3L (latest) and Aspire X3995 firmware version <= P11.A3L (latest) and Aspire XC100 firmware version <= P11.B3 (latest) and Aspire XC600 firmware version <= P11.A4 (latest) and Aspire Z3-615 firmware version <= P11.A2L (latest) and Veriton E430G firmware version <= P21.A1 (latest) and Veriton B630_49 firmware version <= AAP02SR (latest) and Veriton E430 firmware version <= P11.A4 (latest) and Veriton M2110G firmware version <= P21.A3 (latest) and Veriton M2120G fir.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-30426?

It affects 34 products.


Products: Acer Altos T110 F3 Firmware, Acer Ap130 F2 Firmware, Acer Aspire 1600x Firmware, Acer Aspire 1602m Firmware, Acer Aspire 7600u Firmware, Acer Aspire Mc605 Firmware, Acer Aspire Tc-105 Firmware, Acer Aspire Tc-120 Firmware, Acer Aspire U5-620 Firmware, Acer Aspire X1935 Firmware, Acer Aspire X3475 Firmware, Acer Aspire X3995 Firmware, Acer Aspire Xc100 Firmware, Acer Aspire Xc600 Firmware, Acer Aspire Z3-615 Firmware, Acer Veriton B630 49 Firmware, Acer Veriton E430 Firmware, Acer Veriton E430g Firmware, Acer Veriton M2110g Firmware, Acer Veriton M2120g Firmware and 14 more.

## How do I fix CVE-2022-30426?

No fix has been published for CVE-2022-30426 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-30426 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30426 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30426 and fix it if it is affected.

What it is: CVE-2022-30426 is a high-severity memory corruption vulnerability in n/a, published on 22 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30426 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-30426/ (Markdown: https://insights.sbomify.com/CVE-2022-30426/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30426
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30426
- OSV: https://osv.dev/vulnerability/CVE-2022-30426

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-30426/
Summaries are generated and may contain mistakes; the official description above is the record.