CVE-2026-99446
In the Linux kernel, the following vulnerability has been resolved: phy: core: Fix race-condition between _of_phy_get() and try_module_get() Sashiko asked during a patch review if the existing usage pattern had a race condition; specifically in of_phy_get() if it was possible between returning from _of_phy_get() and running try_module_get() that a module might be unbound leading to use-after-free. Looking at the code this appears to be so, there is no linkage between the phy and module under a synchronisation primitive. Using the phy_provider_mutex in phy_get() will ensure there is a link between the returned phy pointer and the module_get() bumping the module reference count. Amend phy_get(), of_phy_get() and devm_of_phy_get_by_index() to fix the same usage pattern. phy_provider_unregister() must take the phy_provider_mutex so amending phy_get()/of_phy_get() to take that same mutex guarantees there is no use-after-free.
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00176
- Cve id
- CVE-2026-99446
- First seen by Signal
- 2026-11-19T15:26:52+00:00
- Name
- CVE-2026-99446
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-19T15:17:58.280
- Last modified
- 2026-11-19T15:17:58.280
- Epss percentile
- 0.07139
Related research
Explore deeper with Ninja Signal's threat intelligence graph