dbcve.org
AndroidOperating system · Google

CVE-2024-32893

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-13
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
In _s5e9865_mif_set_rate of exynos_dvfs.c, there is a possible out of bounds read due to improper casting. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

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 · moderate confidence

An out-of-bounds read vulnerability exists in the Samsung Exynos DVFS (Dynamic Voltage and Frequency Scaling) driver (_s5e9865_mif_set_rate function in exynos_dvfs.c) due to improper type casting. This allows a local attacker to read sensitive information from kernel memory without elevated privileges or user interaction.

MitigationApply Samsung's security patch for the exynos_dvfs.c driver which should include proper type casting and bounds validation. Update to the latest firmware/kernel version for affected Exynos-based 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
AndroidOperating 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 if device uses Exynos SoC
    Check the device's SoC/processor information via /proc/cpuinfo, or using commands like 'getprop ro.hardware' or 'cat /sys/devices/system/cpu/cpu0/cpuinfo' to determine if the chipset is an Samsung Exynos variant.
    Affected if The device runs on an Exynos-based chipset (e.g., Exynos 9xxx, 7xxx, 5xxx series). Non-Exynos devices (e.g., Qualcomm Snapdragon, MediaTek) are not affected by this specific driver vulnerability.
  2. Check if exynos_dvfs driver is present
    Search for the exynos_dvfs kernel module or driver file. Use 'find /lib/modules -name '*exynos*dvfs*' or 'lsmod | grep exynos' to list loaded Exynos-related modules. Also check /sys/module/ for 'exynos_dvfs' or check kernel config for CONFIG_EXYNOS_DVFS.
    Affected if The exynos_dvfs driver is compiled into the kernel or loaded as a module. If the driver is not present (e.g., device uses a different DVFS implementation), the vulnerability cannot be triggered.
  3. Verify kernel version and patch status
    Check the running kernel version via 'uname -r' or 'cat /proc/version'. Cross-reference with Samsung's security bulletins for the month this CVE was patched. Since Android 'all versions' are affected, look for any kernel security update after the CVE disclosure date (April 2024).
    Affected if The kernel lacks the security patch for this CVE - the kernel version predates the fix, or no update has been applied to address the improper type casting in the DVFS driver.
  4. Check for the vulnerable function symbol
    If you have access to the kernel image or can examine /proc/kallsyms, check for the presence of the _s5e9865_mif_set_rate function symbol. Use 'grep -i s5e9865 /proc/kallsyms' or examine the driver binary for this export.
    Affected if The _s5e9865_mif_set_rate function is exported and present in the kernel, indicating the vulnerable code path exists on the device.

The device is affected if it uses an Exynos-based SoC, has the exynos_dvfs driver present, and is running a kernel version predating the CVE-2024-32893 security patch.

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

Apply Samsung's security patch for the exynos_dvfs.c driver which should include proper type casting and bounds validation. Update to the latest firmware/kernel version for affected Exynos-based devices.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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