dbcve.org
YoctoApplication · Linuxfoundation

CVE-2023-32806

MEDIUM · 6.7 CVSS v3.1 Published 2023-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 improper input validation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07441589; Issue ID: ALPS07441589.

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

A vulnerability in the wlan driver allows an out of bounds write due to improper input validation. This enables local privilege escalation to System execution level without requiring user interaction.

MitigationApply vendor patch ALPS07441589 to update the wlan driver and remediate the improper input validation vulnerability.

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
YoctoApplication
Affected:= 4.0
Iot YoctoApplication
Affected:= 23.0
AndroidOperating system
Affected:= 12.0= 13.0
OpenwrtOperating system
Affected:= 21.02.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 the installed product type
    Determine if the system is running one of the affected products: Linuxfoundation Yocto, Mediatek IoT Yocto, Google Android, or OpenWRT. On Linux systems, check /etc/os-release or similar. On Android, check Settings > About Phone > Android version.
    Affected if The system is not one of the listed affected products, the vulnerability does not apply.
  2. Check if wlan driver component is present
    Identify the wlan driver in use. On Linux/Yocto systems, check loaded kernel modules (lsmod) or wireless interface presence (iwconfig or ip link show). On Android, check for wlan interface via settings or dumpsys. On OpenWRT, check network wireless status or /etc/config/wireless.
    Affected if No wlan driver or wireless functionality is present, the vulnerability cannot be exploited.
  3. Verify the exact version of the affected product
    For Linuxfoundation Yocto: check the yocto version in /etc/VERSION or cat /etc/os-release. For Mediatek IoT Yocto: check the version similarly. For Google Android: check Settings > About Phone > Build number or getprop ro.build.version.release. For OpenWRT: check /etc/openwrt_version or cat /etc/os-release.
    Affected if The installed version matches 4.0 (Linuxfoundation Yocto), 23.0 (Mediatek IoT Yocto), 12.0 or 13.0 (Google Android), or 21.02.0 (OpenWRT).
  4. Confirm wlan driver is actively used
    Verify that wireless connectivity has been configured or enabled. Check if wlan interface is up (ip link show wlan0 or similar). On Android, check if WiFi has been turned on at least once. On OpenWRT, check if wireless is enabled in /etc/config/wireless.
    Affected if The wlan driver is loaded and wireless functionality is or has been active, creating the conditions for exploitation.

A user is affected if they are running one of the specified versions (Linuxfoundation Yocto 4.0, Mediatek IoT Yocto 23.0, Google Android 12.0 or 13.0, or OpenWRT 21.02.0) and have an active or previously active wlan driver in the system.

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 vendor patch ALPS07441589 to update the wlan driver and remediate the improper input validation vulnerability.

Fix this in Yocto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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