dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27364

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 Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_roamed_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

This vulnerability exists in Samsung Exynos mobile and wearable processors (models 980, 850, 1080, 1280, 1380, 1330, 1480, W920, W930). The function slsi_rx_roamed_ind() in the kernel driver lacks input validation on a length parameter received from userspace, allowing a malicious userspace application to trigger a heap over-read beyond allocated buffer boundaries.

MitigationThe fix requires adding proper bounds checking on the userspace length parameter before using it to read data into heap buffers, ensuring the length does not exceed the destination buffer size. This is a kernel driver patch requiring Samsung's proprietary kernel source updates.

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 the Exynos processor model
    Check /proc/cpuinfo, /sys/firmware/devicetree/base/model, or use 'lscpu' command to identify the processor. Alternatively, check 'cat /proc/device-tree/model' or 'getprop ro.hardware' on Android devices.
    Affected if The identified model matches any of: Exynos 980, 850, 1080, 1280, 1380, 1330, 1480, W920, or W930. All versions of these models are affected.
  2. Verify the slsi kernel driver is present
    Check for the presence of the Samsung LSI WiFi driver module. Look for files containing 'slsi' in /sys/module/, /proc/modules, or check kernel config CONFIG_SLSI_SAMSUNG_WLAN or similar. The vulnerable function slsi_rx_roamed_ind() exists in drivers/staging/slsi/ or similar paths in Samsung kernel trees.
    Affected if The slsi driver module is loaded or compiled into the kernel, indicating the vulnerable code path is present on the device.
  3. Confirm wireless/WiFi functionality is enabled
    Check if the WiFi interface (typically wlan0) is present via 'ip link show' or 'ifconfig -a'. Also check rfkill status: 'rfkill list all' or check /sys/class/rfkill/ for unblocked wireless adapters.
    Affected if WiFi or wireless connectivity is enabled and the device can communicate with userspace applications, providing the attack surface for the vulnerable function.
  4. Check for userspace access to WiFi driver ioctl or netlink
    Verify that userspace processes can invoke driver functions. Check permissions on /dev/wlan or similar device nodes: 'ls -la /dev/wlan*' or check WiFi socket permissions. The vulnerability requires a malicious userspace app to send crafted input to the driver.
    Affected if The WiFi driver accepts direct ioctl or netlink commands from userspace with insufficient validation, which is the normal operational mode for these drivers.

If the device contains any of the affected Exynos models (980, 850, 1080, 1280, 1380, 1330, 1480, W920, W930) and runs the Samsung kernel driver with WiFi functionality enabled, the device is vulnerable to heap over-read via the slsi_rx_roamed_ind() 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.

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

The fix requires adding proper bounds checking on the userspace length parameter before using it to read data into heap buffers, ensuring the length does not exceed the destination buffer size. This is a kernel driver patch requiring Samsung's proprietary kernel source updates.

Recommended fix Low confidence
  1. Contact Samsung Semiconductor support (semiconductor.samsung.com) to request the firmware security update for your specific Exynos model
  2. Provide the CVE-2024-27364 vulnerability details to your Samsung representative or device vendor
  3. Request the patched firmware version that addresses the missing input validation in slsi_rx_roamed_ind() function
  4. Apply the vendor-provided firmware update through the appropriate update mechanism for your device (OTA or manual flashing)
  5. Verify the update was successfully applied and the vulnerability is remediated

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

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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