dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27378

HIGH · 7.1 CVSS v3.1 Published 2024-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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 · unedited
An issue was discovered in Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330. In the function slsi_send_action_frame_cert(), there is no input validation check on len coming from userspace, which can lead to a heap over-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 · high confidence

Missing input validation on the `len` parameter in the `slsi_send_action_frame_cert()` function allows userspace to specify an arbitrary length value without bounds checking. This enables a heap over-read vulnerability where memory beyond the allocated buffer can be accessed and potentially leaked. The issue affects multiple Exynos mobile processor variants (980, 850, 1280, 1380, 1330) in their Wi-Fi driver firmware.

MitigationImplement proper input validation on the `len` parameter to ensure it does not exceed the allocated buffer size before performing memory operations. Add bounds checking logic and reject or truncate lengths that exceed expected maximum values.

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
Exynos 980 FirmwareOperating system
Affected:all versions
Exynos 850 FirmwareOperating system
Affected:all versions
Exynos 1280 FirmwareOperating system
Affected:all versions
Exynos 1380 FirmwareOperating system
Affected:all versions
Exynos 1330 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device processor variant
    Check the device model number and confirm it contains one of the following Exynos processors: 980, 850, 1280, 1380, or 1330. This information is typically available in the device specifications, system information, or by searching the device model number.
    Affected if The device uses any of the listed Exynos variants (980, 850, 1280, 1380, 1330)
  2. Locate the WiFi driver or firmware version
    Access the device's WiFi firmware or driver information. On Android devices, this may be found in /proc/version, through diagnostic tools like *#*#197328620#*#*, or via vendor-specific engineering menus. Check for files or modules related to the WiFi driver (often named with patterns like slsi, samsung, or vendor-specific identifiers).
    Affected if The WiFi firmware or driver version cannot be determined to be patched, or the device runs on the listed Exynos chips with firmware that has not received a security update addressing this CVE
  3. Verify the vulnerable function exists
    If firmware access is available (e.g., through rooted device, debugging tools, or firmware extraction), search for the function name 'slsi_send_action_frame_cert' within the WiFi driver binary or firmware image.
    Affected if The function slsi_send_action_frame_cert is present in the WiFi driver and no patch has been applied to add bounds checking on the len parameter
  4. Confirm WiFi is enabled and action frame handling is active
    Check that the WiFi interface is operational and that the device processes action frames. This may be observed through network traffic monitoring or driver debug logs if available. The vulnerable code path is only reachable when WiFi is active and action frame certification functions are invoked.
    Affected if WiFi is enabled and the device uses the Samsung WiFi driver with the affected Exynos processors

A defender is affected if they use a Samsung device with an Exynos 980, 850, 1280, 1380, or 1330 processor where the WiFi driver has not been updated with bounds checking on the len parameter in the slsi_send_action_frame_cert function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation on the `len` parameter to ensure it does not exceed the allocated buffer size before performing memory operations. Add bounds checking logic and reject or truncate lengths that exceed expected maximum values.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-27378 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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