dbcve.org
Rtl8195am FirmwareOperating system · Realtek

CVE-2022-34326

HIGH · 7.5 CVSS v3.1 Published 2022-09-27
Fix available
A fix is available. Upgrade to 2022-06-20 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 analysis · high confidence

In the ambiot amb1_sdk for Realtek RTL8195AM devices, a race condition or deadlock exists in Soft AP mode where the timer task and RX task become permanently locked during frequent and continuous Wi-Fi connection failures involving the four-way handshake. This results in a denial of service condition where the device can no longer process Wi-Fi operations or incoming traffic.

MitigationUpdate to amb1_sdk version after 2022-06-20 (commit 284241d70308ff2519e40afd7b284ba892c730a3) or later, which contains the fix for proper task synchronization during failed Wi-Fi handshakes in Soft AP mode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Rtl8195am FirmwareOperating system
Affected:< 2022-06-20

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify RTL8195AM chipset usage
    Determine if the device hardware is based on the Realtek RTL8195AM platform by reviewing device specifications, datasheets, or firmware build information
    Affected if Device does not use RTL8195AM chipset - not affected
  2. Verify Soft AP mode is enabled
    Check device Wi-Fi configuration settings or network logs to confirm Soft AP (Access Point) mode is active
    Affected if Soft AP mode is disabled - not affected regardless of version
  3. Check firmware build date
    Inspect firmware version string, build timestamp, or bootloader information to determine the firmware compilation date for Realtek RTL8195AM
    Affected if Firmware build date is on or after 2022-06-20 - not affected
  4. Look for deadlock symptoms
    Monitor device for complete Wi-Fi operational failure where device stops responding to Wi-Fi connections or incoming traffic, particularly after multiple failed four-way handshakes
    Affected if Device exhibits persistent Wi-Fi deadlock with timer and RX tasks unresponsive - likely affected if version is prior to 2022-06-20

Device is affected only if it uses RTL8195AM chipset with Soft AP mode enabled and has firmware dated before 2022-06-20, and is exhibiting Wi-Fi deadlock symptoms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022-06-20 or later
Fixed in 2022-06-20
Interim mitigation

Update to amb1_sdk version after 2022-06-20 (commit 284241d70308ff2519e40afd7b284ba892c730a3) or later, which contains the fix for proper task synchronization during failed Wi-Fi handshakes in Soft AP mode.

Recommended fix Moderate confidence

Rtl8195am Firmware version released on or after 2022-06-20 (commit 284241d70308ff2519e40afd7b284ba892c730a3)

  1. Identify the current firmware version on the Realtek RTL8195AM device
  2. Navigate to the official Realtek or Ameba IoT support page (www.realtek.com or www.amebaiot.com)
  3. Locate and download the RTL8195AM firmware released on or after 2022-06-20
  4. Follow the official firmware update procedure provided in the device documentation
  5. Verify the upgrade was successful by checking the firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rtl8195am Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA3.0 h
23.0 hours of engineering $3,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,368.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34326 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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