r8169: fix LED-related deadlock on module removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
r8169: fix LED-related deadlock on module removal
Binding devm_led_classdev_register() to the netdev is problematic because on module removal we get a RTNL-related deadlock. Fix this by avoiding the device-managed LED functions.
Note: We can safely call led_classdev_unregister() for a LED even if registering it failed, because led_classdev_unregister() detects this and is a no-op in this case.
From the CVE record · Linux
The Linux kernel's r8169 driver can deadlock during module removal because its device-managed LED registration interacts with RTNL. The input does not establish an attacker-controlled exploit path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the r8169 driver should check their versions; affected versions are not specified.