VYPR
Unrated severityNVD Advisory· Published Jun 5, 2024· Updated Mar 20, 2025

CVE-2024-27380

CVE-2024-27380

Description

In Samsung Exynos 980, 850, 1280, 1380, and 1330, missing length validation in slsi_set_delayed_wakeup_type() allows heap over-read via ioctl.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

In Samsung Exynos 980, 850, 1280, 1380, and 1330, missing length validation in slsi_set_delayed_wakeup_type() allows heap over-read via ioctl.

Vulnerability

In Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330, the function slsi_set_delayed_wakeup_type() in the S.LSI Wi-Fi driver does not validate the length of ioctl_args->args[i] supplied from userspace. This missing input validation enables a heap over-read condition. The vulnerability affects devices using these specific Exynos chipsets [1].

Exploitation

An attacker requires local access to the device and the ability to invoke the vulnerable ioctl call. By crafting an ioctl command with a specially sized ioctl_args->args[i] value that exceeds the expected buffer length, the attacker can trigger a heap over-read. The exact sequence involves sending a malicious ioctl to the affected driver function, exploiting the lack of bounds checking on the user-controlled length parameter.

Impact

Successful exploitation results in reading memory beyond the intended heap buffer, potentially disclosing sensitive information (information disclosure). The attacker gains access to adjacent heap data, which may include cryptographic keys, passwords, or other confidential data processed by the system. The over-read does not directly provide code execution but can leak sensitive kernel or driver memory.

Mitigation

Samsung has released security updates addressing this vulnerability. Affected users should apply the latest firmware and driver updates from Samsung's product security portal [1]. No workarounds are available; updating the device firmware is the only mitigation.

AI Insight generated on May 25, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.