CVE-2023-21058
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 lcsm_SendRrAcquiAssist of lcsm_bcm_assist.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-246169606References: N/A
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 lcsm_SendRrAcquiAssist function in lcsm_bcm_assist.c allows an out-of-bounds write vulnerability in the Android kernel. This memory corruption flaw can be exploited for remote code execution without requiring 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check Android kernel versionRun 'cat /proc/version' or check 'Settings > About Phone > Kernel Version' to identify your kernel buildAffected if Kernel version is older than the March 2023 Android security patch level (or if you cannot confirm the A-246169606 patch was applied)
-
Verify lcsm_bcm_assist module presenceCheck if the lcsm_bcm_assist module exists in your kernel by searching /proc/kallsyms or examining /lib/modules/ for any bcm_assist related kernel modulesAffected if The lcsm_bcm_assist component is loaded in your kernel (this indicates the vulnerable code path exists)
-
Confirm Android security patch levelGo to Settings > About Phone > Build Number (tap repeatedly to enable developer options) then check Settings > System > Developer Options > Security Patch LevelAffected if The Security Patch Level is earlier than March 2023, indicating the bounds check fix has not been applied
If your Android device runs a kernel version predating the March 2023 Android security patch and contains the lcsm_bcm_assist component, you are likely affected by this out-of-bounds write vulnerability.
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.
dbcve · scopedApply the Android kernel security patch for Android ID A-246169606 which adds proper bounds validation in the lcsm_SendRrAcquiAssist function to prevent the out-of-bounds write.
Latest Android OS version with current monthly security patch (check Android Security Bulletin for specific release containing A-246169606 fix)
- 1. Navigate to Settings > System > Security Update on the Android device
- 2. Check for and install the latest Android security patch update
- 3. Verify the installed security patch level includes the fix for A-246169606
- 4. If available, upgrade to the latest Android OS version to ensure kernel-level fixes are included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21058 — 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-2023-21058 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