phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 139ad1143151a07be93bf741d4ea7c89e59f89ce, Kernel 6f901f8448c6b25ed843796b114471d2a3fc5dfb and Kernel c2d7c79898b427d263c64a4841987eec131f2d4e.
In the Linux kernel, the following vulnerability has been resolved: phy: lynx-28g: serialize concurrent phy_set_mode_ext() calls to shared registers The protocol converter configuration registers PCC8, PCCC, PCCD (implemented by the driver), as well as others, control protocol converters from multiple lanes (each represented as a different struct phy). So, if there are simultaneous calls to phy_set_mode_ext() to lanes sharing the same PCC register (either for the "old" or for the "new" protocol), corruption of the values programmed to hardware is possible, because lynx_28g_rmw() has no locking. Add a spinlock in the struct lynx_28g_priv shared by all lanes, and take the global spinlock from the phy_ops :: set_mode() implementation. There are no other callers which modify PCC registers.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.18, >=8f73b37cf3fbda67ea1e579c3b5785da4e7aa2e3 <139ad1143151a07be93bf741d4ea7c89e59f89ce, >=8f73b37cf3fbda67ea1e579c3b5785da4e7aa2e3 <6f901f8448c6b25ed843796b114471d2a3fc5dfb, >=8f73b37cf3fbda67ea1e579c3b5785da4e7aa2e3 <c2d7c79898b427d263c64a4841987eec131f2d4e | 139ad1143151a07be93bf741d4ea7c89e59f89ce, 6f901f8448c6b25ed843796b114471d2a3fc5dfb, c2d7c79898b427d263c64a4841987eec131f2d4e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket