dbcve.org
AndroidOperating system · Google

CVE-2024-29743

HIGH · 7.7 CVSS v3.1 Published 2024-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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_temp_lut 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_temp_lut function of the TMU (Thermal Management Unit) driver (tmu.c) allows an out-of-bounds write to kernel memory. This can be exploited for local privilege escalation without requiring user interaction or additional privileges.

MitigationApply the vendor patch for CVE-2024-29743 which adds proper bounds validation in the tmu_set_temp_lut function to prevent out-of-bounds memory writes.

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

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

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 the target system is running Google Android
    Check /system/build.prop for 'ro.build.version.sdk' or run 'getprop ro.product.model' and 'getprop ro.build.version.release'
    Affected if The system is running any version of Google Android (the vulnerability affects all Android versions)
  2. Identify if the TMU (Thermal Management Unit) kernel driver is present
    Check for the tmu kernel module or driver file in /kernel or /system/lib/modules/, or search kernel config for CONFIG_TMU using /proc/config.gz if available
    Affected if The TMU driver is loaded or compiled into the kernel - the vulnerability exists in the tmu.c driver code
  3. Check if the tmu_set_temp_lut function is accessible
    Inspect the kernel symbols or driver module for the tmu_set_temp_lut function entry point using 'cat /proc/kallsyms | grep tmu_set_temp_lut' if accessible, or examine the compiled driver binary
    Affected if The tmu_set_temp_lut function is present in the loaded kernel or driver module
  4. Determine the Android/Security patch level
    Run 'getprop ro.build.version.security_patch' to check the installed security patch date
    Affected if The security patch level is earlier than the vendor fix date for CVE-2024-29743 (patch date varies by vendor)

A user is affected if the device runs Google Android with the TMU driver containing the vulnerable tmu_set_temp_lut function and the vendor security patch for CVE-2024-29743 has not been applied.

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 CVE-2024-29743 which adds proper bounds validation in the tmu_set_temp_lut function to prevent out-of-bounds memory writes.

Recommended fix Moderate confidence

Latest Android security patch level (check Android Security Bulletin for the specific date containing CVE-2024-29743 fix)

  1. Check the Android Security Bulletin for the patch that addresses CVE-2024-29743 (the vulnerability is in the tmu.c thermal management driver)
  2. Apply the latest Android security patch level to your device or system image
  3. For developers building custom kernels: locate tmu_set_temp_lut in drivers/thermal/tegra/tmu.c (or relevant SoC thermal driver) and add bounds validation on the LUT (Look-Up Table) index/value before writing
  4. Verify the fix includes checking that the index does not exceed the maximum LUT entry count defined for the hardware

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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