CVE-2024-56192
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 wl_notify_gscan_event of wl_cfgscan.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
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 missing bounds check in the wl_notify_gscan_event function of wl_cfgscan.c (a wireless driver component, likely Broadcom) allows an out-of-bounds write. This can be exploited locally for privilege escalation without user interaction or additional privileges.
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 dataall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 wireless driver componentExamine the device's kernel or wireless driver modules for the presence of wl_cfgscan.c or a driver containing the wl_notify_gscan_event function. This may require checking /proc/kallsyms, kernel config, or driver firmware files.Affected if The wl_cfgscan.c driver component with wl_notify_gscan_event function is present on the device
-
Determine driver vendor and versionQuery the wireless driver module information using 'modinfo' if the driver is loadable, or check the driver firmware version through /sys or the vendor's diagnostic tools.Affected if The driver is a Broadcom or similar wl_cfgscan-based wireless driver without the bounds check patch
-
Verify Android security patch levelCheck the device's Android security patch level via Settings > About Phone > Security Patch Level or by running 'getprop ro.build.version.security_patch'Affected if The security patch level is earlier than the vendor release that addresses CVE-2024-56192 (the specific date varies by device vendor)
-
Check kernel symbolsSearch /proc/kallsyms or vmlinux for the wl_notify_gscan_event symbol to confirm the function exists in the running kernel or loaded module.Affected if The wl_notify_gscan_event symbol is found without the bounds validation code
A user is affected if their Android device contains the wl_cfgscan wireless driver with the wl_notify_gscan_event function and lacks the vendor security update that adds proper bounds validation.
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 the vendor patch to the wireless driver that adds proper bounds validation in wl_notify_gscan_event to prevent out-of-bounds memory writes.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56192 — 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-2024-56192 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