dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27365

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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 Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_blockack_ind(), there is no input validation check on a length coming from userspace, which can lead to a potential 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 a length parameter from userspace in the slsi_rx_blockack_ind() function allows a heap over-read vulnerability. The function uses the unvalidated length to read memory from the heap without checking if the length exceeds the allocated buffer size, potentially exposing sensitive data.

MitigationAdd proper input validation bounds checking on the length parameter before performing heap memory operations in slsi_rx_blockack_ind(). Validate that the length does not exceed the allocated buffer size.

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 1080 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
Exynos 1480 FirmwareOperating system
Affected:all versions
Exynos W920 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
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 Exynos chip model
    Check device hardware information through /proc/cpuinfo, device tree files, or system logs. On Android devices, also check /sys/class/hwmon or ls -la /sys/firmware for chip identification.
    Affected if The device uses an Exynos 980, 850, 1080, 1280, 1380, 1330, 1480, or W920 chipset
  2. Locate firmware version
    Retrieve firmware version from device settings (About Phone > Software Information), boot logs, or by checking version files in /vendor/firmware or /system/vendor/firmware directories.
    Affected if Firmware version cannot be determined or is unknown - all versions of listed chips are affected
  3. Verify slsi_rx_blockack_ind function presence
    Examine the WiFi or WLAN firmware binary for the slsi_rx_blockack_ind function symbol. This requires access to the firmware image, typically found in /vendor/firmware/wlan/*.bin or through debugging interfaces.
    Affected if The function slsi_rx_blockack_ind exists in the firmware binary and is used for block ack processing in the WiFi stack

If the device contains any of the listed Exynos chip models (980, 850, 1080, 1280, 1380, 1330, 1480, W920) and runs their firmware, the slsi_rx_blockack_ind function is vulnerable to heap over-read due to missing length validation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add proper input validation bounds checking on the length parameter before performing heap memory operations in slsi_rx_blockack_ind(). Validate that the length does not exceed the allocated buffer size.

Recommended fix Moderate confidence
  1. Monitor Samsung's semiconductor security advisory page (semiconductor.samsung.com) for firmware updates addressing CVE-2024-27365
  2. Apply the latest firmware update for your specific Exynos device through Samsung's official update channels
  3. For mobile devices: Go to Settings > Software Update and install any available security updates
  4. For wearable devices (Exynos W920, W930): Use the companion device app to check for and apply firmware updates
  5. Verify the installed firmware version matches the version containing the security patch
Caveat Firmware updates may have compatibility considerations; ensure backup of device data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27365 — 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-27365 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