CVE-2026-99446
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/090055ee629523092688da42428558ba56d4272f
- git.kernel.org/stable/c/2156c5aefd2c97a60766520bd04f4790f3b38f64
- git.kernel.org/stable/c/2ea5385758a7cc863d9e2f6b642c8e7820437980
- git.kernel.org/stable/c/8a9f16b5237eb5690cc109d37a545f034afa81de
- nvd.nist.gov/vuln/detail/CVE-2026-99446
- cve.org/CVERecord?id=CVE-2026-99446
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.