Description
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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
ff764963479a1b18721ab96e531404c50fefe8b1 to < 2156c5aefd2c97a60766520bd04f4790f3b38f64affectedff764963479a1b18721ab96e531404c50fefe8b1 to < 2ea5385758a7cc863d9e2f6b642c8e7820437980affectedff764963479a1b18721ab96e531404c50fefe8b1 to < 8a9f16b5237eb5690cc109d37a545f034afa81deaffectedff764963479a1b18721ab96e531404c50fefe8b1 to < 090055ee629523092688da42428558ba56d4272faffected
Linux Linux
Default version status: affected
3.13affected0 to < 3.13unaffected6.12.117 to ≤ 6.12.*unaffected6.18.61 to ≤ 6.18.*unaffected7.3.2 to ≤ 7.3.*unaffected7.4-rc1 to ≤ *unaffected