CVE-2024-35986

phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered

HIGH
7
CVSS Score
Published: May 20, 2024 at 09:47 AM UTC
Updated: August 5, 2026 at 12:04 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered The power_supply frame-work is not really designed for there to be long living in kernel references to power_supply devices. Specifically unregistering a power_supply while some other code has a reference to it triggers a WARN in power_supply_unregister(): WARN_ON(atomic_dec_return(&psy->use_cnt)); Folllowed by the power_supply still getting removed and the backing data freed anyway, leaving the tusb1210 charger-detect code with a dangling reference, resulting in a crash the next time tusb1210_get_online() is called. Fix this by only holding the reference in tusb1210_get_online() freeing it at the end of the function. Note this still leaves a theoretical race window, but it avoids the issue when manually rmmod-ing the charger chip driver during development.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.905.18 ≤ v < 6.6.305.18 ≤ v < 6.8.95.18 ≤ v < 6.96.2 ≤ v < 6.6.306.7 ≤ v < 6.8.948969a5623ed918713552e2b4f9d391c89b5e8386.9 rc16.9 rc26.9 rc36.9 rc46.9 rc5
Vendor states this is fixed in 25b3498485ac281e5851700e33b97f12c9533fd8 (fixed)
Vendor states this is fixed in 73224a5d2180066c7fe05b4656647601ba08d588 (fixed)
Vendor states this is fixed in 9827caa5105fb16d1fae2e75c8d0e4662014b3ca (fixed)
Vendor states this is fixed in bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.90 (unaffected)
Vendor states this is fixed in 6.6.30 (unaffected)
Vendor states this is fixed in 6.8.9 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card