dbcve.org
AndroidOperating system · Google

CVE-2024-27204

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 tmu_set_gov_active of tmu.c, there is a possible out of bounds write due to a missing bounds check. 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

An out-of-bounds write vulnerability in the tmu_set_gov_active function of tmu.c (Thermal Management Unit) allows local attackers to escalate privileges to root by writing beyond allocated buffer boundaries due to a missing bounds check. No user interaction or additional execution privileges are required for exploitation.

MitigationApply the vendor patch for this kernel-level vulnerability. If no patch is available, consider disabling or blacklisting the affected TMU kernel module if operationally feasible, or implement compensating controls such as restricting local access to trusted users only.

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. Identify Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Confirm it is exactly 13.0.
    Affected if Android version equals 13.0 (exact match)
  2. Check if TMU kernel module is present
    Look for the TMU thermal driver in /sys/class/thermal/ or check /dev/ for thermal device nodes. On Android, examine /vendor/etc/thermal-config.json or /sys/class/thermal/thermal_zone*/type for 'tmu' or 'thermal-management-unit' entries.
    Affected if TMU/thermal management driver is loaded and accessible on the device
  3. Verify kernel source contains vulnerable function
    If you have access to the device kernel image or source, search for the tmu_set_gov_active function in tmu.c and check if bounds checking is missing before buffer write operations.
    Affected if The compiled kernel includes the tmu_set_gov_active function without proper bounds validation
  4. Confirm local access to device
    This vulnerability is locally exploitable without user interaction. Verify if untrusted local users have shell access or can execute code on the device.
    Affected if Untrusted local users can execute commands on the Android device

A device is affected if it runs Android 13.0 and has the TMU thermal management driver active, allowing any local user to potentially escalate privileges to root.

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 patch for this kernel-level vulnerability. If no patch is available, consider disabling or blacklisting the affected TMU kernel module if operationally feasible, or implement compensating controls such as restricting local access to trusted users only.

Recommended fix Moderate confidence

Android 13.0 with March 2024 Security Patch Level or later; or Android 14 (if device supports it)

  1. Check your device's current Android Security Patch Level under Settings > About Phone > Software Info
  2. If the Security Patch Level is earlier than March 2024, apply the latest available system update for Android 13.0
  3. Go to Settings > System > Software Update and check for updates
  4. If no update is available from your device manufacturer, consider upgrading to Android 14 if your device is supported
Caveat Upgrading to Android 14 may have compatibility issues with apps or device features; some devices may not receive further updates

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
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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