In the Linux kernel, the following vulnerability has been resolved: phy: core: Fix race-condition between _of_phy_get() and try_module_get() Sashiko…
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(
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Linux kernel
- Product
- Linux
- Fix
- available
- Exposure class
- Operating system, Edge / VPN / firewall
- NVD status
- Received
Why it ranks 38 (Notable)
- Exposed product class: edge / VPN / firewall
- Widely deployed vendor product (Linux kernel)
- Fix available
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.
Links
- NIST National Vulnerability Database (CVE API 2.0) (nvd.nist.gov)
- CVE-2026-99446 on this site · NVD · CVE.org · Vulnpedia