CVE-2024-27380

6.0 MEDIUM

📋 TL;DR

This vulnerability in Samsung Exynos mobile processors allows attackers to read heap memory beyond allocated boundaries through a missing input validation check in the slsi_set_delayed_wakeup_type() function. It affects devices using Exynos 980, 850, 1280, 1380, and 1330 chipsets. Attackers can potentially leak sensitive information from kernel memory.

💻 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 systems using affected Exynos chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices with these specific Exynos processors. Requires local access to execute ioctl calls.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Information disclosure of kernel memory contents including sensitive data, cryptographic keys, or pointers that could enable further exploitation.

🟠

Likely Case

Limited information leakage from kernel heap memory, potentially exposing system state information or partial memory contents.

🟢

If Mitigated

No impact if patched or if exploit attempts are blocked by security controls.

🌐 Internet-Facing: LOW - Requires local access to device and ability to execute code.
🏢 Internal Only: MEDIUM - Malicious apps or compromised processes could exploit this vulnerability locally.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires local code execution capability and knowledge of kernel memory layout. No public exploit code available at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Security patches from Samsung (specific version depends on device model and Android version)

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

Restart Required: Yes

Instructions:

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

🔧 Temporary Workarounds

Restrict ioctl access

linux

Limit access to the vulnerable ioctl interface through SELinux policies or kernel module restrictions

🧯 If You Can't Patch

  • Implement strict application sandboxing to limit local code execution capabilities
  • Monitor for suspicious ioctl calls from user applications

🔍 How to Verify

Check if Vulnerable:

Check device processor model in Settings > About Phone > Hardware Information, then verify if security patch level is older than March 2024

Check Version:

getprop ro.boot.hardware (on Android devices via ADB)

Verify Fix Applied:

Verify security patch level is March 2024 or newer in Settings > About Phone > Software Information

📡 Detection & Monitoring

Log Indicators:

  • Kernel logs showing heap corruption warnings
  • SELinux denials for ioctl operations

Network Indicators:

  • No network indicators - local vulnerability only

SIEM Query:

No specific SIEM query - monitor for kernel panic logs or abnormal process behavior

🔗 References

📤 Share & Export