CVE-2023-41112
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 · uneditedAn issue was discovered in Samsung Mobile Processor, Wearable Processor, Automotive Processor, and Modem (Exynos 9810, 9610, 9820, 980, 850, 1080, 2100, 2200, 1280, 1380, 1330, 9110, W920, Modem 5123, Modem 5300, and Auto T5123). A buffer copy, without checking the size of the input, can cause abnormal termination of a mobile phone. This occurs in the RLC task and RLC module.
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 buffer overflow vulnerability exists in the RLC (Radio Link Control) task and module of Samsung's cellular modem firmware across multiple Exynos chipsets. The vulnerability results from copying data to a buffer without validating input size, allowing an attacker to trigger abnormal device termination (denial of service).
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 device chipset modelCheck the device system information or specifications to determine if it uses a Samsung Exynos processor. On Android devices, this can be found in Settings > About Phone > Model, or by using terminal commands like 'getprop ro.hardware' or 'cat /proc/cpuinfo'. Look specifically for Exynos 9810, 9610, 9820, 980, 850, 1080, 2100, or 2200.Affected if The device contains any of the listed Exynos chipsets (9810, 9610, 9820, 980, 850, 1080, 2100, 2200)
-
Determine the baseband modem firmware versionOn Android devices, navigate to Settings > About Phone > Software Information, or use 'getprop gsm.version.baseband' in a terminal. Alternatively, check Settings > Connections > Mobile Networks > Network Mode or similar cellular settings to view the modem firmware version.Affected if The firmware version cannot be verified as updated by Samsung, or the device shows any baseband version for the affected chipsets (all versions are impacted)
-
Verify cellular connectivity is enabledConfirm the device has cellular/Radio Link Control capability active. This is typically indicated by the presence of SIM card status, mobile network bars, or cellular network settings in the device. The RLC module is part of the cellular protocol stack and operates whenever cellular service is active.Affected if Cellular service is enabled and the device connects to mobile networks, as the RLC task runs continuously on active cellular connections
A device is affected if it contains any of the listed Exynos chipsets (9810, 9610, 9820, 980, 850, 1080, 2100, 2200) and uses Samsung baseband firmware, particularly when cellular connectivity is active.
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 vendor-supplied firmware updates from Samsung for affected processors. This is a baseband/modem firmware issue requiring OTA updates from Samsung or device manufacturers; no user-configurable workaround exists.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41112 — 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-41112 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