VYPR
Unrated severityNVD Advisory· Published Jun 5, 2024· Updated Aug 27, 2025

CVE-2024-27372

CVE-2024-27372

Description

A heap overflow in Samsung Exynos mobile processors (980, 850, 1280, 1380, 1330) allows arbitrary write when processing NAN configuration requests.

AI Insight

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

A heap overflow in Samsung Exynos mobile processors (980, 850, 1280, 1380, 1330) allows arbitrary write when processing NAN configuration requests.

Vulnerability

The function slsi_nan_config_get_nl_params() in the Samsung Mobile Processor Exynos 980, Exynos 850, Exynos 1280, Exynos 1380, and Exynos 1330 lacks input validation on disc_attr->infrastructure_ssid_len coming from userspace. This missing check leads to a heap overwrite vulnerability. The affected versions are those that include these specific SoC models.

Exploitation

An attacker must be able to send a crafted NAN (Neighbor Awareness Networking) configuration Netlink message to the kernel driver. No special privileges beyond access to the Netlink socket are required; the attacker needs to control the infrastructure_ssid_len field to cause a heap buffer overflow.

Impact

Successful exploitation allows an attacker to perform a heap overwrite, potentially leading to arbitrary write on the kernel heap. This can result in denial of service or escalation of privileges, possibly allowing full compromise of the device [1].

Mitigation

Samsung has released security updates to address this vulnerability. Users are advised to apply the latest firmware updates from Samsung for the affected Exynos models. The fixed versions are listed in Samsung's Product Security Update portal [1]. No workarounds are available; installing the patch is the recommended 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.