dbcve.org
Linux KernelOperating system · Linux

CVE-2023-20682

MEDIUM · 6.7 CVSS v3.1 Published 2023-04-06
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, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07441605; Issue ID: ALPS07441605.

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 integer overflow to cause an out-of-bounds write, potentially enabling local privilege escalation to System level. The issue requires System execution privileges to exploit but needs no user interaction. This appears to be a kernel/driver-level flaw in wireless firmware.

MitigationApply vendor patch ALPS07441605 which addresses the integer overflow in the wlan driver. Since this is a low-level driver vulnerability, ensure the patch is integrated into the affected device firmware and deployed via OTA update.

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
Linux KernelOperating system
Affected:= 4.19
AndroidOperating system
Affected:= 11.0= 12.0= 13.0
YoctoOperating system
Affected:= 3.1= 3.3= 4.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. Check kernel version for Linux systems
    Run 'uname -r' or check /proc/version to identify the installed kernel version
    Affected if Kernel version is 4.19.x (any patch level)
  2. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Android version is 11.0, 12.0, or 13.0
  3. Check Yocto project version
    Check /etc/lsb-release or run 'cat /etc/os-release' to identify the Yocto version
    Affected if Yocto version is 3.1, 3.3, or 4.0
  4. Identify wlan driver presence
    Check for loaded wireless driver modules via 'lsmod | grep -i wlan' or check /sys/module/ for wlan-related modules
    Affected if Any wlan driver module is loaded on an affected kernel version (4.19) or Android/Yocto system
  5. Confirm system is an Android or embedded Linux device with wireless capability
    Check system type via 'getprop ro.product.device' on Android or check hardware present via 'lspci' or 'lsusb' for wireless adapters on Linux
    Affected if System uses a wlan driver on affected kernel or OS versions

The system is affected if it runs Linux Kernel 4.19, Android 11.0/12.0/13.0, or Yocto 3.1/3.3/4.0 and utilizes the vulnerable wlan driver with integer overflow vulnerability.

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 ALPS07441605 which addresses the integer overflow in the wlan driver. Since this is a low-level driver vulnerability, ensure the patch is integrated into the affected device firmware and deployed via OTA update.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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