dbcve.org
AndroidOperating system · Google

CVE-2024-29783

MEDIUM · 6.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 →
72/100
Remediation priority · Elevated
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_get_tr_thresholds, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure 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

In the tmu_get_tr_thresholds function, an out of bounds read vulnerability exists due to a missing bounds check, allowing a local attacker to read sensitive information from memory without requiring any special privileges or user interaction.

MitigationImplement proper bounds checking in the tmu_get_tr_thresholds function to ensure array indices are validated before access, preventing unauthorized memory reads.

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

CVSS:3.1/AV:L/AC:H/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 device runs Google Android
    Check the operating system by reviewing system properties or /system/build.prop file for 'ro.build.type' and 'ro.build.id' entries indicating Android
    Affected if The device is running any version of Google Android (all versions are affected)
  2. Identify the thermal management driver
    Search kernel modules or driver files for 'tmu' or 'thermal' related components. Look in /proc/config.gz, /boot/config-* or kernel config for CONFIG_EXYNOS_TMU or similar thermal monitoring driver configurations
    Affected if The device uses a thermal management (TMU) driver where the vulnerable tmu_get_tr_thresholds function exists
  3. Check kernel for vulnerable function presence
    If kernel source or symbols are accessible, search for the tmu_get_tr_thresholds function definition. On device, check /proc/kallsyms or extracted kernel modules for this symbol
    Affected if The tmu_get_tr_thresholds function is present in the kernel or thermal driver module without bounds checking
  4. Verify thermal monitoring interface availability
    Check for existence of thermal zone interfaces in /sys/class/thermal/ or through thermal-engine/thermald services that expose thermal threshold reading capabilities
    Affected if Thermal monitoring interfaces are accessible which would allow triggering the out-of-bounds read

If the device runs Google Android and includes a thermal management driver with the tmu_get_tr_thresholds function, the environment is affected by this out-of-bounds read vulnerability.

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

Implement proper bounds checking in the tmu_get_tr_thresholds function to ensure array indices are validated before access, preventing unauthorized memory reads.

Recommended fix Moderate confidence

Android Security Bulletin April 2024 (or subsequent monthly patch)

  1. Check your Android device's current security patch level in Settings > About Phone > Android version > Security patch level
  2. Ensure your device receives the Android Security Bulletin patch that includes CVE-2024-29783. This vulnerability was addressed in the April 2024 Android Security Update.
  3. Apply the latest available system update for your device to receive the security patch containing the fix for tmu_get_tr_thresholds out-of-bounds read.
  4. For Android Open Source Project (AOSP) builds, ensure your kernel includes the bounds check fix in the tmu_get_tr_thresholds function within the thermal management subsystem.
Caveat Monthly security updates are generally low-risk; ensure backup of data before applying updates as standard practice

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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