Security readout for executives and security teams
Plain-English summary
CVE-2021-0475 is an Android Bluetooth flaw that could let a nearby attacker cause memory corruption and potentially run code remotely. The provided sources say no user interaction or added privileges are needed. The source bundle does not show known active exploitation.
Executive priority
Treat this as a high-priority mobile patching issue, especially for fleets with older Android devices and frequent Bluetooth use. There is no source-backed active exploitation claim, but the potential impact is serious.
Technical view
The issue is a use-after-free in Android's on_l2cap_data_ind handling in btif_sock_l2cap.cc. Android classified the impact as possible remote code execution over Bluetooth. The listed affected versions are Android 10 and Android 11. No CVSS, CWE, or exploit evidence is provided in the bundle.
Likely exposure
Exposure is most relevant to Android 10 and Android 11 devices with Bluetooth reachable before receiving the relevant Android security update. Actual exposure depends on OEM patch status, device security patch level, and whether Bluetooth is enabled.
Exploitation context
The source description states remote code execution over Bluetooth may be possible without user interaction or extra privileges. The bundle marks KEV as false and provides no cited evidence of exploitation in the wild.
Researcher notes
Evidence is limited to the CVE description and Android bulletin reference. The bundle does not provide CVSS scoring, CWE mapping, commit details, proof-of-concept status, or vendor-specific device coverage.
Mitigation direction
- Apply OEM Android updates containing the May 2021 Android Security Bulletin fixes.
- Verify affected Android 10 and 11 devices are no longer on vulnerable patch levels.
- Consult OEM or carrier guidance for devices without available updates.
- Prioritize devices that routinely keep Bluetooth enabled in public or shared spaces.
Validation and detection
- Inventory Android 10 and Android 11 devices across managed fleets.
- Check each device's Android security patch level against the May 2021 bulletin.
- Confirm OEM release notes include the relevant Android security fixes.
- Track exceptions for devices unable to receive vendor updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-0475 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/2021-05-01CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.