CVE-2024-35986
"Linux Kernel TI TUSB1210 Power Supply Reference Leak Vulnerability"
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.
INFO
Published Date :
May 20, 2024, 10:15 a.m.
Last Modified :
April 4, 2025, 2:33 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-35986.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-35986 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-35986 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 04, 2025
Action Type Old Value New Value Added CWE CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.30 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.8.9 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.18 up to (excluding) 6.1.90 *cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:* Added Reference Type CVE: https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8 Added Reference https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588 Added Reference https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca Added Reference https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Oct. 29, 2024
Action Type Old Value New Value Added CVSS V3.1 CISA-ADP AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 20, 2024
Action Type Old Value New Value Added 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. Added Reference kernel.org https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-35986 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-35986
weaknesses.