# CVE-2022-32657: Privilege escalation in MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986

> Local attackers with system privileges can exploit incorrect error handling in MediaTek Wi-Fi drivers to escalate privileges.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-3wp9-gvwq-96mc

## What is CVE-2022-32657?

CVE-2022-32657 is a medium-severity vulnerability in MediaTek, Inc. MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986, published on 3 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: GN20220705042; Issue ID: GN20220705042.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

It affects 10 products.


Products: Mediatek Mt7603 Firmware, Mediatek Mt7613 Firmware, Mediatek Mt7615 Firmware, Mediatek Mt7622 Firmware, Mediatek Mt7628 Firmware, Mediatek Mt7629 Firmware, Mediatek Mt7915 Firmware, Mediatek Mt7916 Firmware, Mediatek Mt7981 Firmware, Mediatek Mt7986 Firmware.

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

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

## Is CVE-2022-32657 being exploited?

There is no known exploitation of CVE-2022-32657 in the wild and no public exploit code.

## Other vulnerabilities in MediaTek, Inc. MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986

- [CVE-2022-32658](https://insights.sbomify.com/CVE-2022-32658/): Privilege escalation in MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986 (medium 6.7)
- [CVE-2022-32659](https://insights.sbomify.com/CVE-2022-32659/): Privilege escalation in MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986, MT8518S, MT8532 (medium 6.7)
- [CVE-2022-26438](https://insights.sbomify.com/CVE-2022-26438/): Memory corruption in MT7603, MT7610, MT7612, MT7613, MT7615, MT7620, MT7622, MT7628, MT7629, MT7915, MT7916, MT7986, MT8981 (medium 6.7)
- [CVE-2022-26439](https://insights.sbomify.com/CVE-2022-26439/): Memory corruption in MT7603, MT7610, MT7612, MT7613, MT7615, MT7620, MT7622, MT7628, MT7629, MT7915, MT7916, MT7986, MT8981 (medium 6.7)
- [CVE-2022-26440](https://insights.sbomify.com/CVE-2022-26440/): Memory corruption in MT7603, MT7610, MT7612, MT7613, MT7615, MT7620, MT7622, MT7628, MT7629, MT7915, MT7916, MT7986, MT8981 (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32657 is a medium-severity vulnerability in MediaTek, Inc. MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986, published on 3 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-32657 in the wild and no public exploit code.

Affected product: MediaTek, Inc. MT7603, MT7613, MT7615, MT7622, MT7628, MT7629, MT7915, MT7916, MT7981, MT7986. 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-32657/ (Markdown: https://insights.sbomify.com/CVE-2022-32657/index.md)
```

## Sources

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

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