# CVE-2022-34326: Denial of service in n/a

> Frequent Wi-Fi connection failures in Soft AP mode cause task locking, leading to denial of service on Realtek RTL8195AM devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-f75q-r8vf-45pj

## What is CVE-2022-34326?

CVE-2022-34326 is a high-severity denial of service vulnerability in n/a, published on 27 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ambiot amb1_sdk (aka SDK for Ameba1) before 2022-06-20 on Realtek RTL8195AM devices before 284241d70308ff2519e40afd7b284ba892c730a3, the timer task and RX task would be locked when there are frequent and continuous Wi-Fi connection (with four-way handshake) failures in Soft AP mode.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Realtek Rtl8195am Firmware.

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

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

## Is CVE-2022-34326 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-39306](https://insights.sbomify.com/CVE-2021-39306/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-43573](https://insights.sbomify.com/CVE-2021-43573/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-9395](https://insights.sbomify.com/CVE-2020-9395/): Memory corruption in n/a (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34326 is a high-severity denial of service vulnerability in n/a, published on 27 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34326 in the wild and no public exploit code.

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-34326/ (Markdown: https://insights.sbomify.com/CVE-2022-34326/index.md)
```

## Sources

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

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