CVE-2024-35986
phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered
Reported by linux · Published May 20, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.8.9, 6.6.30, 6.1.90 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838 |
| Linux | Linux | 5.18, 0, 6.1.90 |
| linux | linux_kernel | 5.18, 5.18, 5.18 |
| Linux | Linux | 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838 |
Timeline
- May 20, 2024 CVE Published
- May 21, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (8 in total, the first dated here)
- Dec 16, 2025 PoC Published
- Jan 10, 2026 Security Advisory (429 in total, the first dated here)
- Mar 31, 2026 Distribution Patch (324 in total, the first dated here)
- Nov 2, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-35986
vulnetix vdb fixes CVE-2024-35986
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-35986/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart