CVE-2024-26723: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix crash when adding interface under a lag There is a crash when adding one of the lan966x interfaces under a lag interface. The issue can be reproduced like this: ip link add name bond0 type bond miimon 100 mode balance-xor ip link set dev eth0 master bond0 The reason is because when adding a interface under the lag it would go through all the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have ports that are NULL pointer as they are not probed. So then iterating over these ports it would just crash as they are NULL pointers. The fix consists in actually checking for NULL pointers before accessing something from the ports. Like we do in other places.
AI Analysis
Technical Summary
CVE-2024-26723 is a high-severity vulnerability in the Linux kernel affecting the lan966x network driver, specifically when adding an interface under a Link Aggregation Group (LAG) interface. The vulnerability arises due to improper handling of NULL pointers during the iteration over ports associated with the LAG interface. When a lan966x interface is added under a LAG, the kernel code attempts to enumerate all ports to identify which belong to the LAG. However, some ports may not have been probed and thus are represented as NULL pointers. The lack of NULL pointer checks leads to a kernel crash (denial of service) when the code dereferences these NULL pointers. The issue can be reproduced by creating a bond interface (e.g., bond0) with mode balance-xor and adding a lan966x interface (e.g., eth0) as a slave to this bond. The fix implemented involves adding proper NULL pointer checks before accessing port data, preventing the crash. The vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption) due to the crash impact. The CVSS v3.1 base score is 7.8 (high), with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating local attack vector, low attack complexity, requires low privileges, no user interaction, unchanged scope, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild as of the publication date (April 3, 2024).
Potential Impact
For European organizations, this vulnerability poses a significant risk primarily to systems running Linux kernels with the lan966x driver in environments utilizing Link Aggregation (bonding) for network interfaces. The crash caused by the NULL pointer dereference results in kernel panic or system instability, leading to denial of service. This can disrupt critical network infrastructure, especially in data centers, telecommunications, and enterprise environments relying on bonded interfaces for redundancy and load balancing. The high impact on confidentiality and integrity suggests that the crash could be leveraged in complex attack scenarios to escalate privileges or cause data corruption, although direct exploitation details are limited. Given the prevalence of Linux in European IT infrastructure, including servers, network appliances, and embedded systems, the vulnerability could affect a broad range of sectors such as finance, healthcare, government, and industrial control systems. The requirement for local privileges and low complexity means that insider threats or attackers with limited access could trigger the crash, potentially as part of a larger attack chain. The absence of user interaction simplifies exploitation in controlled environments. Overall, the vulnerability threatens availability and reliability of critical networked systems in Europe.
Mitigation Recommendations
European organizations should prioritize patching Linux kernels to versions that include the fix for CVE-2024-26723. Specifically, kernel updates that add NULL pointer checks in the lan966x driver should be applied promptly. In environments where immediate patching is not feasible, administrators should consider temporarily disabling the use of lan966x interfaces under LAG configurations or avoid creating bond interfaces with lan966x ports until patched. Network monitoring should be enhanced to detect unusual crashes or reboots related to bonding interfaces. Access controls should be tightened to restrict local user privileges, minimizing the risk of exploitation by low-privilege users. Additionally, organizations should audit their network interface configurations to identify the presence of lan966x devices and bonded interfaces. For embedded or specialized devices using lan966x, vendors should be contacted for firmware updates or mitigations. Implementing kernel crash dump analysis can help in early detection of exploitation attempts. Finally, integrating this vulnerability into vulnerability management and incident response workflows will ensure timely detection and remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2024-26723: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix crash when adding interface under a lag There is a crash when adding one of the lan966x interfaces under a lag interface. The issue can be reproduced like this: ip link add name bond0 type bond miimon 100 mode balance-xor ip link set dev eth0 master bond0 The reason is because when adding a interface under the lag it would go through all the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have ports that are NULL pointer as they are not probed. So then iterating over these ports it would just crash as they are NULL pointers. The fix consists in actually checking for NULL pointers before accessing something from the ports. Like we do in other places.
AI-Powered Analysis
Technical Analysis
CVE-2024-26723 is a high-severity vulnerability in the Linux kernel affecting the lan966x network driver, specifically when adding an interface under a Link Aggregation Group (LAG) interface. The vulnerability arises due to improper handling of NULL pointers during the iteration over ports associated with the LAG interface. When a lan966x interface is added under a LAG, the kernel code attempts to enumerate all ports to identify which belong to the LAG. However, some ports may not have been probed and thus are represented as NULL pointers. The lack of NULL pointer checks leads to a kernel crash (denial of service) when the code dereferences these NULL pointers. The issue can be reproduced by creating a bond interface (e.g., bond0) with mode balance-xor and adding a lan966x interface (e.g., eth0) as a slave to this bond. The fix implemented involves adding proper NULL pointer checks before accessing port data, preventing the crash. The vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption) due to the crash impact. The CVSS v3.1 base score is 7.8 (high), with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating local attack vector, low attack complexity, requires low privileges, no user interaction, unchanged scope, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild as of the publication date (April 3, 2024).
Potential Impact
For European organizations, this vulnerability poses a significant risk primarily to systems running Linux kernels with the lan966x driver in environments utilizing Link Aggregation (bonding) for network interfaces. The crash caused by the NULL pointer dereference results in kernel panic or system instability, leading to denial of service. This can disrupt critical network infrastructure, especially in data centers, telecommunications, and enterprise environments relying on bonded interfaces for redundancy and load balancing. The high impact on confidentiality and integrity suggests that the crash could be leveraged in complex attack scenarios to escalate privileges or cause data corruption, although direct exploitation details are limited. Given the prevalence of Linux in European IT infrastructure, including servers, network appliances, and embedded systems, the vulnerability could affect a broad range of sectors such as finance, healthcare, government, and industrial control systems. The requirement for local privileges and low complexity means that insider threats or attackers with limited access could trigger the crash, potentially as part of a larger attack chain. The absence of user interaction simplifies exploitation in controlled environments. Overall, the vulnerability threatens availability and reliability of critical networked systems in Europe.
Mitigation Recommendations
European organizations should prioritize patching Linux kernels to versions that include the fix for CVE-2024-26723. Specifically, kernel updates that add NULL pointer checks in the lan966x driver should be applied promptly. In environments where immediate patching is not feasible, administrators should consider temporarily disabling the use of lan966x interfaces under LAG configurations or avoid creating bond interfaces with lan966x ports until patched. Network monitoring should be enhanced to detect unusual crashes or reboots related to bonding interfaces. Access controls should be tightened to restrict local user privileges, minimizing the risk of exploitation by low-privilege users. Additionally, organizations should audit their network interface configurations to identify the presence of lan966x devices and bonded interfaces. For embedded or specialized devices using lan966x, vendors should be contacted for firmware updates or mitigations. Implementing kernel crash dump analysis can help in early detection of exploitation attempts. Finally, integrating this vulnerability into vulnerability management and incident response workflows will ensure timely detection and remediation.
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-02-19T14:20:24.163Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d982ac4522896dcbe3929
Added to database: 5/21/2025, 9:08:58 AM
Last enriched: 7/3/2025, 1:41:21 AM
Last updated: 8/17/2025, 10:55:49 PM
Views: 11
Related Threats
CVE-2025-33090: CWE-1333 Inefficient Regular Expression Complexity in IBM Concert Software
HighCVE-2025-27909: CWE-942 Permissive Cross-domain Policy with Untrusted Domains in IBM Concert Software
MediumCVE-2025-1759: CWE-244 Improper Clearing of Heap Memory Before Release ('Heap Inspection') in IBM Concert Software
MediumCVE-2025-4962: CWE-284 Improper Access Control in lunary-ai lunary-ai/lunary
HighCVE-2025-36120: CWE-863 Incorrect Authorization in IBM Storage Virtualize
HighActions
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.