CVE-2024-27383

6.7 MEDIUM

📋 TL;DR

A heap overflow vulnerability in Samsung Exynos mobile processors allows attackers to overwrite heap memory by sending unvalidated data to the slsi_get_scan_extra_ies() function. This affects Samsung devices using Exynos 980, 850, 1280, 1380, and 1330 chipsets, potentially enabling arbitrary code execution or system crashes.

💻 Affected Systems

Products:
  • Samsung Mobile Processor Exynos 980
  • Samsung Mobile Processor Exynos 850
  • Samsung Mobile Processor Exynos 1280
  • Samsung Mobile Processor Exynos 1380
  • Samsung Mobile Processor Exynos 1330
Versions: All versions prior to security patch
Operating Systems: Android-based Samsung devices
Default Config Vulnerable: ⚠️ Yes
Notes: Affects Samsung smartphones and tablets using these specific Exynos chipsets. Vulnerability is in the Wi-Fi driver component.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full device compromise with kernel-level code execution, allowing complete control over affected Samsung mobile devices.

🟠

Likely Case

Device instability, crashes, or denial of service through heap corruption, potentially leading to privilege escalation.

🟢

If Mitigated

Limited impact if patched or if exploit attempts are blocked by security controls, though device may still experience instability.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires sending specially crafted data to the vulnerable function, which may be accessible via local or network vectors depending on device configuration.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Samsung security updates for specific device models

Vendor Advisory: https://semiconductor.samsung.com/support/quality-support/product-security-updates/

Restart Required: Yes

Instructions:

1. Check for Samsung security updates in device settings. 2. Apply the latest available security patch. 3. Reboot device after installation.

🔧 Temporary Workarounds

Disable Wi-Fi when not needed

android

Reduces attack surface by disabling the vulnerable Wi-Fi component

Use trusted networks only

android

Limit Wi-Fi connections to known, secure networks to reduce exposure

🧯 If You Can't Patch

  • Isolate affected devices from untrusted networks
  • Monitor for unusual device behavior or crashes

🔍 How to Verify

Check if Vulnerable:

Check device model and chipset in Settings > About phone, then verify against affected Exynos models

Check Version:

Not applicable via command line on consumer devices

Verify Fix Applied:

Check security patch level in Settings > About phone > Software information and ensure it's after the vulnerability disclosure date

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic logs
  • Wi-Fi driver crash reports
  • Unexpected system reboots

Network Indicators:

  • Unusual Wi-Fi scan requests
  • Malformed network packets targeting Wi-Fi interfaces

SIEM Query:

Not typically applicable for mobile device monitoring

🔗 References

📤 Share & Export