CVE-2022-25818
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 · uneditedImproper boundary check in UWB stack prior to SMR Mar-2022 Release 1 allows arbitrary code execution.
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 confidenceImproper boundary check (buffer overflow) in the UWB (Ultra-Wideband) communication stack allows arbitrary code execution. This memory corruption vulnerability exists due to missing bounds checking in the UWB stack processing, enabling attackers to overflow buffers and inject malicious code on affected devices running versions prior to SMR Mar-2022 Release 1.
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= 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
- 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.
-
Verify Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is exactly 12.0 (Android 12.0)
-
Check if device has UWB hardwareCheck device specifications for UWB (Ultra-Wideband) support, or inspect /system/etc/ for UWB-related files, or run 'getprop | grep uwb' via ADBAffected if Device contains UWB-capable hardware (chipset supports IEEE 802.15.4z)
-
Confirm UWB functionality is enabledCheck Settings > Connections > UWB (or similar path depending on device), or inspect if UWB system service is active via 'dumpsys' commandAffected if UWB feature toggle is turned on or UWB system service is running
-
Check security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Security patch level is earlier than SMR March 2022 release (e.g., February 2022 or older)
Device is affected if it runs Android 12.0, has UWB hardware enabled, and lacks the SMR Mar-2022 security update containing the boundary check fix.
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 · scopedUpdate UWB firmware, drivers, or associated software components to SMR Mar-2022 Release 1 or later to incorporate the boundary check fix. Prioritize patching exposed or internet-facing UWB-enabled devices given the critical severity.
SMR Mar-2022 Release 1 or later (Security Patch Level March 2022)
- 1. Navigate to Settings on your Samsung Android device
- 2. Go to Settings > Security & Privacy (or Settings > Biometrics and security)
- 3. Tap on Security policy updates or check for updates
- 4. Ensure the device is updated to SMR (Samsung Maintenance Release) March-2022 or later
- 5. Alternatively, check for system software updates via Settings > Software update > Download and install
- 6. Verify the security patch level is March 2022 or higher in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25818 — 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-25818 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