dbcve.org
Exynos 980 FirmwareOperating system · Samsung

CVE-2024-27368

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 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_received_frame_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

A missing input validation vulnerability in the Samsung Exynos driver function slsi_rx_received_frame_ind() allows a malicious userspace application to supply an arbitrary length value without bounds checking. This causes the kernel to read beyond the allocated heap buffer, potentially exposing sensitive kernel memory contents to userland.

MitigationSamsung should implement proper input validation on the userspace-supplied length parameter in slsi_rx_received_frame_ind() to ensure it does not exceed the allocated buffer size before use. Users should apply vendor-provided firmware/security updates for affected Exynos devices.

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 chip model in the device
    Check device hardware specifications, boot logs, or system information to determine which Exynos processor is present. Common methods include: 'cat /proc/cpuinfo' on Android devices, checking 'lspci' or 'lsusb' output, reviewing the device's technical specifications from manufacturer documentation, or examining boot-up kernel messages via 'dmesg'
    Affected if The device uses any of these Exynos models: 980, 850, 1080, 1280, 1380, 1330, 1480, or W920
  2. Locate the slsi driver or firmware components
    Search for Samsung LSI (slsi) driver files in the kernel or firmware directories. Common paths may include /lib/firmware/, /system/lib/, or kernel driver directories. Look for files containing 'slsi', 'wlan', 'wifi', or 'r4' in the firmware directory
    Affected if The slsi_rx_received_frame_ind() function exists in the loaded driver or firmware, indicating the vulnerable code path is present
  3. Verify userspace can interact with the WiFi driver interface
    Check if the WiFi subsystem is active and has userspace interfaces available. This may involve checking for WiFi being enabled, examining network interfaces (iw list, ip link show), or verifying the wlan driver is loaded
    Affected if WiFi is enabled and the Samsung slsi WiFi driver is active, allowing userspace applications to invoke the vulnerable slsi_rx_received_frame_ind() function
  4. Confirm firmware version (if determinable)
    Read the firmware version from the Exynos WiFi firmware files or driver debug interfaces. Check /sys/class/net/wlan*/firmware_version, or read firmware file metadata, or use 'strings' on firmware binaries to find version strings
    Affected if The device runs any firmware version on the affected Exynos chips listed (all versions are affected per the advisory)

If the device contains any of the affected Exynos chips (980, 850, 1080, 1280, 1380, 1330, 1480, W920) and has the slsi WiFi driver active, the device is vulnerable to kernel memory exposure via the unchecked length parameter in slsi_rx_received_frame_ind().

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

Samsung should implement proper input validation on the userspace-supplied length parameter in slsi_rx_received_frame_ind() to ensure it does not exceed the allocated buffer size before use. Users should apply vendor-provided firmware/security updates for affected Exynos devices.

Fix this in Exynos 980 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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