dbcve.org
AndroidOperating system · Google

CVE-2024-31333

HIGH · 7.8 CVSS v3.1 Published 2024-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 _MMU_AllocLevel of mmu_common.c, there is a possible arbitrary code execution due to an integer overflow. This could lead to local escalation of privilege in the kernel 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

Integer overflow vulnerability in the kernel's MMU memory allocation function (_MMU_AllocLevel in mmu_common.c) allows a local attacker to trigger insufficient memory allocation, potentially leading to arbitrary code execution with kernel privileges and local privilege escalation.

MitigationApply the kernel security patch for this vulnerability and update to a patched kernel version; given the high-severity kernel-level flaw, prioritize deployment to affected systems.

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 the kernel version
    Run 'uname -a' or read /proc/version to obtain the installed Android kernel version
    Affected if The kernel version is earlier than the patched version for CVE-2024-31333 (the vulnerability affects all unpatched versions)
  2. Verify MMU support is enabled
    Check kernel configuration for MMU support (CONFIG_MMU=y) via /proc/config.gz or check if /sys/kernel/debug/kernel_config exists, or review kernel boot parameters
    Affected if MMU is disabled (the vulnerable _MMU_AllocLevel function is only invoked when MMU is enabled, so if MMU is disabled the specific flaw does not apply)
  3. Check for the vulnerable MMU allocation function
    Inspect the kernel image or source for the _MMU_AllocLevel function in mmu_common.c - verify if the vulnerable integer overflow check exists
    Affected if The function contains the vulnerable allocation logic without proper integer overflow validation
  4. Review kernel security patch level
    Run 'getprop ro.build.version.security_patch' on Android to check the installed security patch level
    Affected if The security patch level is earlier than the month the CVE was patched

A system is affected if it runs an unpatched Android kernel with MMU enabled and the vulnerable _MMU_AllocLevel function present in the kernel memory management code.

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 kernel security patch for this vulnerability and update to a patched kernel version; given the high-severity kernel-level flaw, prioritize deployment to affected systems.

Recommended fix Moderate confidence

Apply all available Android Security Bulletins. For precise fixed release, refer to the Android Security Bulletin for the month this CVE was addressed (source.android.com/security-bulletin)

  1. Apply the latest Android Security Bulletin patch for your Android version. Check Settings > Security > Security update for available updates
  2. Ensure your device is running the latest kernel security patches. Manufacturers typically bundle these with monthly security updates
  3. If your device manufacturer has released a specific kernel update addressing CVE-2024-31333, apply that update immediately
  4. For enterprise or custom ROM users, ensure the kernel is updated to a version incorporating the fix for the integer overflow in _MMU_AllocLevel in mmu_common.c
Caveat Kernel patches are generally low-risk but should be tested in controlled environments before production deployment on custom/unlocked devices

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 / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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