CVE-2024-50023: net: phy: Remove LED entry from LEDs list on unregister
In the Linux kernel, the following vulnerability has been resolved:
net: phy: Remove LED entry from LEDs list on unregister
Commit c938ab4da0eb ("net: phy: Manual remove LEDs to ensure correct ordering") correctly fixed a problem with using devm but missed removing the LED entry from the LEDs list.
This cause kernel panic on specific scenario where the port for the PHY is torn down and up and the kmod for the PHY is removed.
On setting the port down the first time, the assosiacted LEDs are correctly unregistered. The associated kmod for the PHY is now removed. The kmod is now added again and the port is now put up, the associated LED are registered again. On putting the port down again for the second time after these step, the LED list now have 4 elements. With the first 2 already unregistered previously and the 2 new one registered again.
This cause a kernel panic as the first 2 element should have been removed.
Fix this by correctly removing the element when LED is unregistered.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50023?
The severity of CVE-2024-50023 is considered moderate due to potential impacts on stability.
How do I fix CVE-2024-50023?
To fix CVE-2024-50023, update your Linux kernel to the latest version that includes the patch.
Which versions of Linux Kernel are affected by CVE-2024-50023?
CVE-2024-50023 affects Linux Kernel versions between 6.4 and 6.6.57, as well as certain 6.7 and 6.12 release candidates.
What does CVE-2024-50023 involve?
CVE-2024-50023 involves an issue in the Linux kernel related to LED entry removal from the LEDs list upon device unregistration.
Is there a workaround for CVE-2024-50023?
Currently, there is no known workaround for CVE-2024-50023, and upgrading to a patched version is recommended.