CVE-2025-27374
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 the Secure Boot component in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850, 1080, 1280, 2200, 1330, 1380, 1480, 2400. The lack of a length check leads to out-of-bounds writes.
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 missing length check in the Secure Boot component of Samsung Exynos processors (9820, 9825, 980, 990, 850, 1080, 1280, 2200, 1330, 1380, 1480, 2400) allows out-of-bounds memory writes during the boot verification process. This could potentially enable an attacker to corrupt memory and potentially bypass secure boot protections.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 Exynos processor model in the deviceCheck the device's system information, boot logs, or specifications. On Samsung mobile devices, this can be found in Settings > About Phone > Processor info, or via terminal commands like 'cat /proc/cpuinfo'. For other devices, consult the hardware specifications or bootloader logs.Affected if The processor model matches one of the following: Exynos 9820, 9825, 980, 850, 1080, 1280, 2200, 1330, 1380, 1480, 2400, or 990.
-
Verify the firmware version installedAccess the device's firmware version information. On Samsung devices: Settings > About Phone > Software Version. Check the build number or firmware revision. For embedded systems, inspect the bootloader or secure boot manifest.Affected if The device is running any firmware version on an affected Exynos processor (the advisory states all versions are affected).
-
Confirm Secure Boot is enabledCheck the device's secure boot status. This may be visible in the bootloader (UEFI/ARM Trusted Firmware logs), secure boot configuration settings, or through diagnostic tools that query the trusted execution environment.Affected if Secure Boot is enabled and the device uses an affected Exynos processor, as the vulnerability exists in the Secure Boot verification process itself.
-
Review boot verification logs for anomaliesExamine boot logs or trusted boot measurements for signs of memory corruption, unexpected writes, or verification failures during the boot chain. Look for errors related to secure boot validation or memory access violations.Affected if Boot logs show memory corruption events or verification failures occurring during the secure boot chain on an affected processor.
The device is affected if it contains any of the listed Exynos processors (9820, 9825, 980, 850, 1080, 1280, 2200, 1330, 1380, 1480, 2400, 990) with Secure Boot enabled, regardless of firmware version.
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-provided firmware updates from Samsung for affected processors. Since this is a hardware/firmware-level vulnerability in the Secure Boot chain, no workarounds are available; patching is required.
- 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-2025-27374 — 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-2025-27374 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