CVE-2023-21075
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 get_svc_hash of nan.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-261857862References: 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 · moderate confidenceA heap buffer overflow vulnerability exists in the get_svc_hash function of nan.cpp in the Android kernel's NAN (Neighbor Awareness Networking) component. The flaw allows an attacker to write beyond allocated buffer boundaries, potentially achieving local privilege escalation 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 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
- 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.
-
Verify if WiFi Aware (NAN) is enabled on the deviceOn the Android device, go to Settings > Network & Internet > Wi-Fi > Wi-Fi preferences, or check via shell: 'settings get secure wifi_aware_enabled'Affected if WiFi Aware is turned ON - the vulnerable get_svc_hash function in the NAN component is only accessible when NAN is enabled, and exploitation requires this feature to be active
-
Check the Android Security Patch LevelGo to Settings > About Phone > Android version, or use shell command: 'getprop ro.build.version.security_patch'Affected if The patch level is earlier than the fix date for A-261857862 (the security bulletin that addressed this issue) - all versions before the patch are affected
-
Confirm the device is running Google AndroidCheck system property: 'getprop ro.product.device' or 'getprop ro.build.fingerprint' - verify it is a Google Android build and not a forked ROM with separate patchingAffected if The device runs a standard Google Android build - this vulnerability is specific to Android kernel NAN component as described in the CVE
-
Check kernel NAN component status (if accessible)If you have root access, check for the nan.ko module: 'ls -la /system/lib/modules/' or check /proc/kallsyms for get_svc_hash symbol presenceAffected if The NAN kernel module is loaded and the get_svc_hash function is present in the kernel - this confirms the vulnerable code path exists
A device is affected if it runs any unpatched Android version with WiFi Aware (NAN) enabled and has not received the security patch addressing A-261857862.
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 Android security patch level that addresses A-261857862. For developers, this requires reviewing and fixing bounds checking in the get_svc_hash function within the NAN component to ensure proper validation of buffer sizes before write operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21075 — 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-21075 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