dbcve.org
AndroidOperating system · Google

CVE-2022-47364

MEDIUM · 5.5 CVSS v3.1 Published 2023-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 wlan driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service in wlan services.

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 · moderate confidence

An out-of-bounds write vulnerability exists in a WLAN driver due to a missing bounds check. This allows a local attacker to write data beyond allocated memory boundaries, potentially causing a denial of service in WLAN services.

MitigationApply the vendor-provided security update or patch for the affected WLAN driver to implement proper bounds checking. If no patch is available, consider updating to a newer driver version or contacting the device manufacturer.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release' via ADB
    Affected if Version is exactly 10.0, 11.0, or 12.0
  2. Verify WLAN is enabled
    Check Settings > Network & Internet > Wi-Fi, or run 'adb shell settings get global wifi_on'
    Affected if WLAN is turned on (value returned is not 0)
  3. Identify WLAN driver module
    Run 'adb shell ls -la /system/lib/modules/' or 'adb shell getprop wlan.driver.version' to locate the WLAN driver
    Affected if A WLAN driver module exists in the system (indicates WLAN hardware is present)
  4. Check WLAN driver build date or patch level
    Run 'adb shell dumpsys wifi' and look for driver version strings, or check 'adb shell getprop ro.build.version.security_patch'
    Affected if Security patch level is earlier than the vendor fix date for this CVE

Device is affected if running Android 10.0, 11.0, or 12.0 with WLAN enabled, and the WLAN driver has not been patched to include bounds checking fixes.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security update or patch for the affected WLAN driver to implement proper bounds checking. If no patch is available, consider updating to a newer driver version or contacting the device manufacturer.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47364 — 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-47364 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