CVE-2026-99446
phy: core: Fix race-condition between _of_phy_get() and try_module_get()
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: ff764963479a1b18721ab96e531404c50fefe8b1 to < 2156c5aefd2c97a60766520bd04f4790f3b38f64; affected: ff764963479a1b18721ab96e531404c50fefe8b1 to < 2ea5385758a7cc863d9e2f6b642c8e7820437980; affected: ff764963479a1b18721ab96e531404c50fefe8b1 to < 8a9f16b5237eb5690cc109d37a545f034afa81de; affected: ff764963479a1b18721ab96e531404c50fefe8b1 to < 090055ee629523092688da42428558ba56d4272f | See vendor advisory |
| LinuxLinux | affected: 3.13; unaffected: 0 to < 3.13; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99446
- https://git.kernel.org/stable/c/2156c5aefd2c97a60766520bd04f4790f3b38f64
- https://git.kernel.org/stable/c/2ea5385758a7cc863d9e2f6b642c8e7820437980
- https://git.kernel.org/stable/c/8a9f16b5237eb5690cc109d37a545f034afa81de
- https://git.kernel.org/stable/c/090055ee629523092688da42428558ba56d4272f