dbcve.org
AndroidOperating system · Google

CVE-2024-27219

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

A missing bounds check in the tmu_set_pi function of tmu.c (Thermal Management Unit) allows an out-of-bounds write, enabling local privilege escalation without requiring user interaction or additional execution privileges.

MitigationAdd proper bounds checking in the tmu_set_pi function before performing the write operation to prevent out-of-bounds memory access.

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. Confirm Android version is 13.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The Android version is exactly 13.0 (not 12.x, 14.x, or other variants)
  2. Verify TMU (Thermal Management Unit) driver is present
    Check for tmu.ko or tmu driver module in /sys/module/ or /proc/modules, or look for 'tmu' references in /proc/device-tree/ on devices with device tree
    Affected if The TMU thermal management driver module is loaded or compiled into the kernel
  3. Identify the kernel version in use
    Run 'uname -r' via ADB shell or check /proc/version
    Affected if The kernel is a mainline or vendor-specific build that includes the tmu.c driver code from Android 13.0 base
  4. Check if thermal monitoring interfaces are accessible
    Examine /sys/class/thermal/ for thermal zone directories, or check /dev/ for tmu-related device nodes if exposed
    Affected if Thermal Management Unit interfaces are exposed and accessible on the device
  5. Review kernel source for tmu_set_pi function
    If you have kernel source access, search for tmu_set_pi function in tmu.c and verify if bounds checking exists before array write operations
    Affected if The tmu_set_pi function lacks proper bounds validation before performing write operations

A device is affected if it runs Android version 13.0 exactly and contains the vulnerable TMU (Thermal Management Unit) driver with the tmu_set_pi function lacking bounds checking.

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

Add proper bounds checking in the tmu_set_pi function before performing the write operation to prevent out-of-bounds memory access.

Recommended fix Moderate confidence

Android 13.0 with March 2024 Security Patch Level, or Android 14.0/15.0 which contain the fix

  1. 1. Go to Settings on the affected Android device
  2. 2. Navigate to System > System Update
  3. 3. Check for and install any available system updates
  4. 4. Ensure the device receives the March 2024 Android Security Patch Level or later which addresses CVE-2024-27219
  5. 5. After updating, verify the Security Patch Level in Settings > About Phone > Android version shows the patched security date
Caveat Standard OS upgrade considerations apply - backup data before updating, and verify app compatibility after upgrade

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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