CVE-2023-30652
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 bounds read and write in callrunTspCmdNoRead of sysinput HAL service prior to SMR Jul-2023 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 · high confidenceThis is an out-of-bounds read/write vulnerability in the sysinput HAL (Hardware Abstraction Layer) service, specifically in the callrunTspCmdNoRead function. Local attackers can exploit this to execute arbitrary code on affected devices running SMR versions prior to July 2023 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= 11.0= 12.0= 13.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, or run 'getprop ro.build.version.release' via ADBAffected if Version is 11.0, 12.0, or 13.0
-
Confirm the device is a Samsung modelGo to Settings > About Phone > Model number, or run 'getprop ro.product.model' via ADBAffected if Device is a Samsung product (the sysinput HAL is Samsung-specific)
-
Check the SMR versionRun 'getprop ro.build.version.sem' via ADB to retrieve the Samsung Maintenance Release versionAffected if SMR version is present and is earlier than July 2023 Release 1 (the SMR date code would be before 2023-07)
-
Verify the sysinput HAL service existsRun 'getprop sys.hal.input' or check for sysinput HAL daemon processes via 'ps -A | grep sysinput' via ADBAffected if The sysinput HAL service is present and running on the device
A Samsung Android device on version 11.0, 12.0, or 13.0 with an SMR version earlier than July 2023 Release 1 that has the sysinput HAL service enabled is affected by this vulnerability.
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 July 2023 Release 1 or later firmware update to the affected device to patch the vulnerable sysinput HAL service.
SMR Jul-2023 Release 1 or later
- Check current security patch level: Go to Settings > About Phone > Software Information > Security patch level
- Verify your device model is eligible for SMR Jul-2023 Release 1 by checking security.samsungmobile.com
- If eligible, go to Settings > Software Update
- Tap Download and install to apply the July 2023 security update
- Verify the security patch level shows July 2023 or later after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30652 — 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-30652 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