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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 23.10 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 14.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 16.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
git.kernel.org/linus/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 (6.9-rc6)
git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052
launchpad.net/bugs/cve/CVE-2024-35986
nvd.nist.gov/vuln/detail/CVE-2024-35986
security-tracker.debian.org/tracker/CVE-2024-35986
www.cve.org/CVERecord?id=CVE-2024-35986