dbcve.org
AndroidOperating system · Google

CVE-2024-27236

HIGH · 8.4 CVSS v3.1 Published 2024-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges 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 aoc_unlocked_ioctl of aoc.c, there is a possible memory corruption due to type confusion. This could lead to local escalation of privilege 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 · high confidence

A type confusion vulnerability in the aoc_unlocked_ioctl function of the Linux kernel aoc driver allows memory corruption leading to local privilege escalation. The flaw occurs when the driver improperly handles data type validation in ioctl command processing, potentially allowing an attacker to corrupt memory and gain elevated privileges.

MitigationApply the vendor-provided kernel driver patch for CVE-2024-27236 to the aoc driver, or update to a kernel version containing the fix. Ensure the aoc driver is not loaded or used if no patch is available.

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:= 13.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Verify it is exactly 13.0.
    Affected if Android version is 13.0 AND the aoc driver is present on the device
  2. Verify aoc driver presence
    Check for the aoc driver module in /sys/module/ or /kernel/drivers/ (path varies by device). Use 'ls /sys/module/ | grep aoc' or search the kernel build configuration for CONFIG_ something similar to 'aoc' or 'AOC'.
    Affected if The aoc driver module exists in the kernel
  3. Confirm aoc driver is loaded or in use
    Check if the aoc driver is loaded using 'lsmod | grep aoc' or check /proc/modules. Also verify if /dev/aoc or similar device nodes exist (ls -la /dev/*aoc*).
    Affected if The aoc driver is loaded as a kernel module or has active device nodes
  4. Check kernel version for fix status
    Run 'uname -a' to get kernel version. Compare against the kernel version in the vendor security bulletin for CVE-2024-27236. If the vendor has released a fix, the installed kernel should be later than the fixed version.
    Affected if Kernel version is older than the fixed version listed in the vendor security bulletin for this CVE

A device is affected if it runs Android 13.0 with the aoc driver present and the kernel version predates the vendor fix for CVE-2024-27236.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided kernel driver patch for CVE-2024-27236 to the aoc driver, or update to a kernel version containing the fix. Ensure the aoc driver is not loaded or used if no patch is available.

Recommended fix High confidence

Android 14 or later (or the latest Android security patch level for Android 13 provided by the device vendor)

  1. 1. Upgrade the device from Android 13.0 to Android 14 or later to receive the security patch addressing the type confusion vulnerability in aoc.c
  2. 2. Alternatively, if available from the device manufacturer, apply the specific Android security patch level that includes the fix for CVE-2024-27236
  3. 3. Verify the Android version and security patch level after update via Settings > About Phone > Android version
Caveat Android 14 upgrade may have app compatibility considerations; review app compatibility before major deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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