dbcve.org
AndroidOperating system · Google

CVE-2024-25992

HIGH · 7.8 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 →
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 tmu_tz_control of tmu.c, there is a possible out of bounds read 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 thermal management unit (TMU) driver vulnerability in tmu.c allows an unprivileged local user to read out-of-bounds memory via the tmu_tz_control function due to a missing bounds check. This memory read can be weaponized to leak kernel memory addresses and achieve local privilege escalation to root. User interaction is not required.

MitigationApply the vendor-supplied kernel/firmware patch that adds proper bounds validation in the tmu_tz_control function. If no patch is available, consider disabling the TMU interface or restricting access through SELinux policies until an update is released.

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
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. Confirm Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version. The affected version is exactly 13.0.
    Affected if The version returned is 13.0 (exact match)
  2. Verify TMU driver presence
    Check for TMU thermal management driver in /proc/modules, /sys/module/ or by searching for 'tmu' in /proc/kallsyms. On Android, the driver may be built into the kernel image rather than as a loadable module.
    Affected if The TMU driver (tmu, tmu_tz, or similar thermal management module) is loaded or compiled into the kernel
  3. Check for TMU device node
    Look for thermal management device nodes such as /dev/tmu, /dev/tmu_tz, or entries under /sys/class/thermal/ that reference 'tmu' in their name.
    Affected if A TMU-related device node or sysfs entry exists on the device
  4. Verify kernel symbol availability
    Check if the tmu_tz_control function symbol exists in the running kernel by examining /proc/kallsyms or using 'grep tmu /proc/kallsyms' if available.
    Affected if The tmu_tz_control symbol is exported and present in the kernel symbol table

You are affected if the device runs Android 13.0 exactly AND has the TMU thermal management driver enabled or present in the kernel.

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-supplied kernel/firmware patch that adds proper bounds validation in the tmu_tz_control function. If no patch is available, consider disabling the TMU interface or restricting access through SELinux policies until an update is released.

Recommended fix Moderate confidence

Android 14 (or later security patch level) - the vulnerability was addressed in subsequent Android security updates beyond Android 13.0

  1. Check your Android device manufacturer for the latest available security patch level
  2. Apply the latest Android security update available for your device, which should include the fix for this vulnerability in the thermal management driver (tmu.c)
  3. If your device is no longer receiving security updates, consider upgrading to a device that currently receives monthly security patches
  4. Verify the applied patch level includes the CVE-2024-25992 fix via your device's security settings or manufacturer documentation
Caveat Upgrading to Android 14 may introduce app compatibility issues; ensure critical apps are compatible before proceeding

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-25992 — 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-25992 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