CVE-2022-25821
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 use of SMS buffer pointer in Shannon baseband prior to SMR Mar-2022 Release 1 allows OOB read.
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 confidenceThis vulnerability exists in Samsung's Shannon baseband processor firmware. The issue involves improper handling of an SMS buffer pointer, which allows an out-of-bounds read operation. The flaw affects devices running baseband firmware versions prior to the SMR March 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= 10.0= 11.0= 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the baseband chipsetCheck the device specifications or use system information tools to determine if the device uses a Samsung Shannon baseband processor chipset.Affected if The device does not use a Samsung Shannon baseband chipset, then this specific CVE does not apply.
-
Retrieve the baseband firmware versionObtain the baseband firmware version from the device. This is typically accessible through phone information settings, engineering menus, or by querying the baseband modem via AT commands (such as AT+CGMR or AT+CGMM) if available.Affected if Unable to retrieve or unknown baseband version.
-
Compare the baseband version to the affected rangeCompare your retrieved baseband firmware version against the SMR March 2022 Release 1 baseline. Determine if the installed version is earlier than this release.Affected if The baseband firmware version is prior to the SMR March 2022 Release 1.
-
Verify Android OS versionConfirm the Android OS version running on the device (10.0, 11.0, or 12.0).Affected if The device runs Android 10.0, 11.0, or 12.0 in combination with an affected baseband version.
The device is affected if it uses a Samsung Shannon baseband chipset with firmware prior to SMR March 2022 Release 1, running Android 10, 11, or 12.
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 · scopedOrganizations should identify affected Samsung devices using Shannon baseband chipsets and apply the vendor-provided baseband firmware update (SMR Mar-2022 Release 1 or later). Coordinate with mobile carriers for patch deployment.
SMR Mar-2022 Release 1
- Check the current Android version and Samsung firmware version on the device in Settings > About Phone
- Navigate to Settings > Software Update on the Samsung device
- Download and install the SMR (Samsung Monthly Release) March 2022 Release 1 or later firmware update
- Restart the device if prompted and verify the update was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25821 — 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-25821 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