CVE-2022-32590
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 · uneditedIn wlan, there is a possible use after free due to an incorrect status check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07299425; Issue ID: ALPS07299425.
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 confidenceA use-after-free vulnerability exists in the WLAN component due to an incorrect status check. This allows a local attacker to escalate privileges to System level without requiring user interaction.
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= 3.1= 3.3= 11.0= 12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Yocto or Android versionOn Yocto, run 'cat /etc/os-release' or check the build configuration. On Android, check 'ro.build.version.release' via 'getprop ro.build.version.release' or in Settings > About Phone.Affected if The version is exactly 3.1 or 3.3 for Yocto, or exactly 11.0 or 12.0 for Android.
-
Verify the WLAN component is enabledCheck if the WLAN interface exists by running 'ip link show' or 'iw dev' on Yocto, or check Wi-Fi is available in Android settings and confirm the wlan0 interface exists via 'ip link'.Affected if A WLAN interface (such as wlan0) is present and active.
-
Identify the WLAN driver in useOn Yocto, run 'lsmod' to list loaded kernel modules and look for WLAN-related modules such as ath10k, ath11k, iwlwifi, brcmfmac, or similar. On Android, check 'getprop | grep wlan' to retrieve WLAN driver details.Affected if A WLAN driver module is loaded.
-
Check for the specific vulnerable driver status check logicInspect the WLAN driver source or binary for the status check routine mentioned in the CVE. On Yocto, this would require checking the kernel config or driver version: 'modinfo <wlan_driver_module>' to retrieve version details.Affected if The driver version matches the vulnerable releases that have not been patched with ALPS07299425.
You are affected if you are running Yocto 3.1 or 3.3, or Android 11.0 or 12.0, with an active WLAN interface using the vulnerable driver that lacks the ALPS07299425 patch.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patch ALPS07299425 to correct the status check logic in the WLAN driver and eliminate the use-after-free condition.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-32590 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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