CVE-2024-35986
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.1.90
- Linux Kernel < 6.6.30
- Linux Kernel < 6.8.9
- Linux Kernel 6.9
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-35986.md and follow it. Check whether this project is affected by CVE-2024-35986. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
- https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
- https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
- https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052
- https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
- https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
- https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
- https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052
References
- https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
- https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
- https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
- https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052
- https://git.kernel.org/stable/c/25b3498485ac281e5851700e33b97f12c9533fd8
- https://git.kernel.org/stable/c/73224a5d2180066c7fe05b4656647601ba08d588
- https://git.kernel.org/stable/c/9827caa5105fb16d1fae2e75c8d0e4662014b3ca
- https://git.kernel.org/stable/c/bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052