CVE-2024-42142: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-switch, Create ingress ACL when needed Currently, ingress acl is used for three features. It is created only when vport metadata match and prio tag are enabled. But active-backup lag mode also uses it. It is independent of vport metadata match and prio tag. And vport metadata match can be disabled using the following devlink command: # devlink dev param set pci/0000:08:00.0 name esw_port_metadata \ value false cmode runtime If ingress acl is not created, will hit panic when creating drop rule for active-backup lag mode. If always create it, there will be about 5% performance degradation. Fix it by creating ingress acl when needed. If esw_port_metadata is true, ingress acl exists, then create drop rule using existing ingress acl. If esw_port_metadata is false, create ingress acl and then create drop rule.
AI Analysis
Technical Summary
CVE-2024-42142 is a vulnerability identified in the Linux kernel's Mellanox mlx5 Ethernet switch (E-switch) driver component, specifically related to the handling of ingress Access Control Lists (ACLs) in active-backup Link Aggregation Group (LAG) mode. The ingress ACL is a mechanism used to filter or drop network packets entering a virtual port (vport) on the E-switch. Previously, the ingress ACL was created only when certain features were enabled, namely vport metadata matching and priority tagging. However, the active-backup LAG mode also relies on ingress ACLs independently of these features. If the ingress ACL is not created when active-backup LAG mode is used, attempting to create a drop rule triggers a kernel panic, causing a denial of service. The vulnerability arises because the ingress ACL creation logic did not account for active-backup LAG mode unless vport metadata match or priority tagging was enabled. The fix involves conditionally creating the ingress ACL whenever it is needed: if the esw_port_metadata parameter is true and an ingress ACL exists, the drop rule uses the existing ACL; if esw_port_metadata is false, the ingress ACL is created before applying the drop rule. This approach resolves the panic issue while minimizing performance degradation, which would be about 5% if the ACL were always created regardless of need. The vulnerability affects specific Linux kernel versions identified by commit hashes and was published on July 30, 2024. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of denial of service through kernel panics on systems using the affected Linux kernel versions with Mellanox mlx5 E-switch drivers configured in active-backup LAG mode. Such configurations are common in data centers and enterprise environments that rely on high-availability network setups and advanced network interface card (NIC) features for load balancing and redundancy. A kernel panic can disrupt critical services, leading to downtime and potential loss of productivity. While this vulnerability does not directly enable remote code execution or privilege escalation, the resulting service interruptions could impact business operations, especially in sectors with stringent uptime requirements such as finance, telecommunications, and cloud service providers. Additionally, the performance trade-off in the fix (approximately 5% degradation) may affect high-throughput environments, requiring careful consideration during patch deployment. Since no exploits are currently known, the immediate risk is moderate, but organizations should proactively patch to prevent future exploitation and maintain network stability.
Mitigation Recommendations
European organizations should apply the patch or updated Linux kernel version that includes the fix for CVE-2024-42142 as soon as it becomes available. In the interim, administrators can verify and adjust the esw_port_metadata parameter using the devlink command to ensure ingress ACLs are created appropriately, preventing kernel panics. Specifically, running 'devlink dev param set pci/0000:08:00.0 name esw_port_metadata value true cmode runtime' can help maintain ingress ACL presence if active-backup LAG mode is in use. Network teams should audit their use of active-backup LAG mode with Mellanox mlx5 drivers and test the impact of enabling ingress ACL creation on performance to balance stability and throughput. Monitoring kernel logs for panic events related to ingress ACLs can provide early detection of issues. Finally, organizations should incorporate this vulnerability into their patch management and vulnerability scanning processes to ensure timely remediation and compliance with security policies.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-42142: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-switch, Create ingress ACL when needed Currently, ingress acl is used for three features. It is created only when vport metadata match and prio tag are enabled. But active-backup lag mode also uses it. It is independent of vport metadata match and prio tag. And vport metadata match can be disabled using the following devlink command: # devlink dev param set pci/0000:08:00.0 name esw_port_metadata \ value false cmode runtime If ingress acl is not created, will hit panic when creating drop rule for active-backup lag mode. If always create it, there will be about 5% performance degradation. Fix it by creating ingress acl when needed. If esw_port_metadata is true, ingress acl exists, then create drop rule using existing ingress acl. If esw_port_metadata is false, create ingress acl and then create drop rule.
AI-Powered Analysis
Technical Analysis
CVE-2024-42142 is a vulnerability identified in the Linux kernel's Mellanox mlx5 Ethernet switch (E-switch) driver component, specifically related to the handling of ingress Access Control Lists (ACLs) in active-backup Link Aggregation Group (LAG) mode. The ingress ACL is a mechanism used to filter or drop network packets entering a virtual port (vport) on the E-switch. Previously, the ingress ACL was created only when certain features were enabled, namely vport metadata matching and priority tagging. However, the active-backup LAG mode also relies on ingress ACLs independently of these features. If the ingress ACL is not created when active-backup LAG mode is used, attempting to create a drop rule triggers a kernel panic, causing a denial of service. The vulnerability arises because the ingress ACL creation logic did not account for active-backup LAG mode unless vport metadata match or priority tagging was enabled. The fix involves conditionally creating the ingress ACL whenever it is needed: if the esw_port_metadata parameter is true and an ingress ACL exists, the drop rule uses the existing ACL; if esw_port_metadata is false, the ingress ACL is created before applying the drop rule. This approach resolves the panic issue while minimizing performance degradation, which would be about 5% if the ACL were always created regardless of need. The vulnerability affects specific Linux kernel versions identified by commit hashes and was published on July 30, 2024. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of denial of service through kernel panics on systems using the affected Linux kernel versions with Mellanox mlx5 E-switch drivers configured in active-backup LAG mode. Such configurations are common in data centers and enterprise environments that rely on high-availability network setups and advanced network interface card (NIC) features for load balancing and redundancy. A kernel panic can disrupt critical services, leading to downtime and potential loss of productivity. While this vulnerability does not directly enable remote code execution or privilege escalation, the resulting service interruptions could impact business operations, especially in sectors with stringent uptime requirements such as finance, telecommunications, and cloud service providers. Additionally, the performance trade-off in the fix (approximately 5% degradation) may affect high-throughput environments, requiring careful consideration during patch deployment. Since no exploits are currently known, the immediate risk is moderate, but organizations should proactively patch to prevent future exploitation and maintain network stability.
Mitigation Recommendations
European organizations should apply the patch or updated Linux kernel version that includes the fix for CVE-2024-42142 as soon as it becomes available. In the interim, administrators can verify and adjust the esw_port_metadata parameter using the devlink command to ensure ingress ACLs are created appropriately, preventing kernel panics. Specifically, running 'devlink dev param set pci/0000:08:00.0 name esw_port_metadata value true cmode runtime' can help maintain ingress ACL presence if active-backup LAG mode is in use. Network teams should audit their use of active-backup LAG mode with Mellanox mlx5 drivers and test the impact of enabling ingress ACL creation on performance to balance stability and throughput. Monitoring kernel logs for panic events related to ingress ACLs can provide early detection of issues. Finally, organizations should incorporate this vulnerability into their patch management and vulnerability scanning processes to ensure timely remediation and compliance with security policies.
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-07-29T15:50:41.189Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9827c4522896dcbe1b7e
Added to database: 5/21/2025, 9:08:55 AM
Last enriched: 6/29/2025, 5:40:47 AM
Last updated: 8/16/2025, 1:14:38 PM
Views: 15
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
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.