CVE-2024-34614
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 · uneditedOut-of-bound write in libsmat.so prior to SMR Aug-2024 Release 1 allows local attackers to execute arbitrary code.
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 confidenceAn out-of-bounds write vulnerability exists in the libsmat.so library in versions prior to the SMR Aug-2024 Release 1. This memory corruption flaw allows local attackers to achieve arbitrary code execution by exploiting the improper bounds checking when writing to memory.
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.0= 13.0= 14.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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify the Android versionGo to Settings > About Phone > Android version and note the version numberAffected if The version is 12.0, 13.0, or 14.0 (or any version within these release lines prior to the August 2024 update)
-
Locate the libsmat.so librarySearch for the file libsmat.so in the system library directories (typically /system/lib64/ or /system/lib/)Affected if The libsmat.so library is present on the device and was not updated in the SMR Aug-2024 Release 1 patch
-
Check the Samsung SMR versionGo to Settings > About Phone > Software information and look for the SMR (Samsung Maintenance Release) version or build numberAffected if The SMR version is earlier than the August 2024 Release 1, or the security patch level is dated before August 2024
You are affected if your device runs Android 12.0, 13.0, or 14.0, contains the libsmat.so library, and has not received the SMR Aug-2024 Release 1 security update.
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 SMR Aug-2024 Release 1 or later update that patches the libsmat.so library to address the out-of-bounds write vulnerability.
SMR Aug-2024 Release 1 or later
- 1. Navigate to Settings on your Samsung Galaxy device
- 2. Tap on 'Software update' or 'System update'
- 3. Tap 'Download and install' to check for available updates
- 4. Ensure the device updates to SMR Aug-2024 Release 1 or later which contains the fix for the out-of-bounds write vulnerability in libsmat.so
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,584.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34614 — 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-2024-34614 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