CVE-2024-29749
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 · uneditedIn tmu_set_tr_thresholds 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 confidenceAn out-of-bounds write vulnerability exists in the tmu_set_tr_thresholds function within the TMU (Thermal Management Unit) driver (tmu.c). The function fails to validate array bounds before writing threshold values, allowing a local attacker to write beyond allocated buffer boundaries and potentially escalate privileges to root.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android kernel versionRun 'uname -r' or check Settings > About Phone > Kernel Version to obtain the running kernel version. Compare it to the version that includes the vendor patch containing proper bounds checking in tmu_set_tr_thresholds.Affected if The kernel version is older than the patched version and has not received the bounds-checking fix.
-
Identify TMU driver presenceCheck if the Thermal Management Unit driver is loaded by running 'lsmod | grep tmu' or looking for tmu.ko in /lib/modules/. Also check /proc/devices for thermal management related entries.Affected if The TMU driver (tmu.ko or compiled into the kernel) is present and loaded on the device.
-
Verify driver source fileIf you have access to the kernel source or driver binaries, examine tmu.c and locate the tmu_set_tr_thresholds function. Check if bounds validation exists before array writes (look for index validation or array boundary checks).Affected if The tmu_set_tr_thresholds function lacks proper index/bounds validation before writing threshold values to arrays.
-
Check thermal subsystem configurationExamine the device's thermal zone configuration in /sys/class/thermal/ or check /dev/ for TMU-related device nodes. The vulnerability requires the TMU thermal driver to be actively managing thermal thresholds.Affected if The TMU thermal driver is actively managing thermal zones and accepting threshold configurations.
The device is affected if it runs any version of Google Android with the TMU driver loaded and a kernel that does not include the bounds-checking fix in the tmu_set_tr_thresholds function.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied kernel/driver patch which adds proper bounds checking to the tmu_set_tr_thresholds function to validate threshold indices before writing. Update to the latest kernel version containing the fix.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29749 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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