CVE-2024-50023: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-50023 is a vulnerability in the Linux kernel related to the handling of PHY (physical layer) device LEDs during port state changes and module reloads. Specifically, the issue arises in the kernel's network PHY driver code where LED entries are not properly removed from the internal LED list upon unregistration. The problem stems from an incomplete fix in commit c938ab4da0eb, which addressed manual removal of LEDs to ensure correct ordering but failed to fully remove LED entries from the list. The vulnerability manifests when a network port associated with a PHY device is brought down, causing the associated LEDs to unregister correctly and the PHY kernel module (kmod) to be removed. When the module is reloaded and the port is brought back up, the LEDs are registered again. However, if the port is subsequently brought down a second time, the LED list contains duplicate entries—some already unregistered and some newly registered—leading to inconsistent internal state. This inconsistency triggers a kernel panic, effectively causing a denial of service (DoS) condition on the affected system. The vulnerability is triggered by a specific sequence of port down/up operations combined with PHY module reloads, which may be encountered in dynamic network environments or during device driver reloads. The root cause is a failure to correctly remove LED list elements upon unregistration, which the patch aims to fix by ensuring proper cleanup of LED entries. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with affected PHY drivers, particularly in environments where network interfaces are dynamically managed or PHY modules are frequently reloaded. The kernel panic induced by this flaw results in system crashes, causing temporary denial of service. This can disrupt critical network infrastructure, servers, or embedded devices relying on Linux, impacting availability. Organizations operating data centers, telecommunications infrastructure, or industrial control systems using Linux-based devices are at risk of operational interruptions. While the vulnerability does not directly expose confidentiality or integrity risks, the availability impact can lead to service outages, affecting business continuity and potentially causing financial and reputational damage. Since exploitation requires specific conditions (port down/up sequences and module reloads), the threat is more relevant in environments with active network reconfiguration or driver updates. European sectors such as finance, healthcare, manufacturing, and public services that depend on stable Linux-based networking equipment could be affected if patches are not applied promptly.
Mitigation Recommendations
To mitigate CVE-2024-50023, European organizations should: 1) Apply the official Linux kernel patches that correctly remove LED entries upon unregistration as soon as they are available from trusted sources or Linux distributions. 2) Monitor and control the dynamic reloading of PHY kernel modules and network port state changes, minimizing unnecessary port down/up cycles especially in production environments. 3) Implement robust system monitoring to detect kernel panics or unexpected reboots that may indicate attempts to trigger this vulnerability. 4) For critical systems, consider isolating network interfaces or using redundant network paths to maintain availability during maintenance or driver reloads. 5) Engage with Linux distribution vendors to ensure timely updates and backports for affected kernel versions. 6) Conduct thorough testing of kernel updates in staging environments to validate stability and absence of regressions related to PHY LED handling. 7) Educate system administrators about the specific conditions triggering this vulnerability to avoid inadvertent exposure during routine network management.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Finland
CVE-2024-50023: Vulnerability in Linux Linux
Description
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-50023 is a vulnerability in the Linux kernel related to the handling of PHY (physical layer) device LEDs during port state changes and module reloads. Specifically, the issue arises in the kernel's network PHY driver code where LED entries are not properly removed from the internal LED list upon unregistration. The problem stems from an incomplete fix in commit c938ab4da0eb, which addressed manual removal of LEDs to ensure correct ordering but failed to fully remove LED entries from the list. The vulnerability manifests when a network port associated with a PHY device is brought down, causing the associated LEDs to unregister correctly and the PHY kernel module (kmod) to be removed. When the module is reloaded and the port is brought back up, the LEDs are registered again. However, if the port is subsequently brought down a second time, the LED list contains duplicate entries—some already unregistered and some newly registered—leading to inconsistent internal state. This inconsistency triggers a kernel panic, effectively causing a denial of service (DoS) condition on the affected system. The vulnerability is triggered by a specific sequence of port down/up operations combined with PHY module reloads, which may be encountered in dynamic network environments or during device driver reloads. The root cause is a failure to correctly remove LED list elements upon unregistration, which the patch aims to fix by ensuring proper cleanup of LED entries. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with affected PHY drivers, particularly in environments where network interfaces are dynamically managed or PHY modules are frequently reloaded. The kernel panic induced by this flaw results in system crashes, causing temporary denial of service. This can disrupt critical network infrastructure, servers, or embedded devices relying on Linux, impacting availability. Organizations operating data centers, telecommunications infrastructure, or industrial control systems using Linux-based devices are at risk of operational interruptions. While the vulnerability does not directly expose confidentiality or integrity risks, the availability impact can lead to service outages, affecting business continuity and potentially causing financial and reputational damage. Since exploitation requires specific conditions (port down/up sequences and module reloads), the threat is more relevant in environments with active network reconfiguration or driver updates. European sectors such as finance, healthcare, manufacturing, and public services that depend on stable Linux-based networking equipment could be affected if patches are not applied promptly.
Mitigation Recommendations
To mitigate CVE-2024-50023, European organizations should: 1) Apply the official Linux kernel patches that correctly remove LED entries upon unregistration as soon as they are available from trusted sources or Linux distributions. 2) Monitor and control the dynamic reloading of PHY kernel modules and network port state changes, minimizing unnecessary port down/up cycles especially in production environments. 3) Implement robust system monitoring to detect kernel panics or unexpected reboots that may indicate attempts to trigger this vulnerability. 4) For critical systems, consider isolating network interfaces or using redundant network paths to maintain availability during maintenance or driver reloads. 5) Engage with Linux distribution vendors to ensure timely updates and backports for affected kernel versions. 6) Conduct thorough testing of kernel updates in staging environments to validate stability and absence of regressions related to PHY LED handling. 7) Educate system administrators about the specific conditions triggering this vulnerability to avoid inadvertent exposure during routine network management.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-10-21T12:17:06.065Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9824c4522896dcbdfd09
Added to database: 5/21/2025, 9:08:52 AM
Last enriched: 6/28/2025, 4:25:43 PM
Last updated: 7/25/2025, 12:28:05 PM
Views: 12
Related Threats
CVE-2025-8833: Stack-based Buffer Overflow in Linksys RE6250
HighCVE-2025-7965: CWE-352 Cross-Site Request Forgery (CSRF) in CBX Restaurant Booking
MediumCVE-2025-8832: Stack-based Buffer Overflow in Linksys RE6250
HighCVE-2025-8831: Stack-based Buffer Overflow in Linksys RE6250
HighCVE-2025-8829: OS Command Injection in Linksys RE6250
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.