LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38557: net/mlx5: Reload only IB representors upon lag disable/enable

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Reload only IB representors upon lag disable/enable On lag disable, the bond IB device along with all of its representors are destroyed, and then the slaves' representors get reloaded. In case the slave IB representor load fails, the eswitch error flow unloads all representors, including ethernet representors, where the netdevs get detached and removed from lag bond. Such flow is inaccurate as the lag driver is not responsible for loading/unloading ethernet representors. Furthermore, the flow described above begins by holding lag lock to prevent bond changes during disable flow. However, when reaching the ethernet representors detachment from lag, the lag lock is required again, triggering the following deadlock: Call trace: __switch_to+0xf4/0x148 __schedule+0x2c8/0x7d0 schedule+0x50/0xe0 schedule_preempt_disabled+0x18/0x28 __mutex_lock.isra.13+0x2b8/0x570 __mutex_lock_slowpath+0x1c/0x28 mutex_lock+0x4c/0x68 mlx5_lag_remove_netdev+0x3c/0x1a0 [mlx5_core] mlx5e_uplink_rep_disable+0x70/0xa0 [mlx5_core] mlx5e_detach_netdev+0x6c/0xb0 [mlx5_core] mlx5e_netdev_change_profile+0x44/0x138 [mlx5_core] mlx5e_netdev_attach_nic_profile+0x28/0x38 [mlx5_core] mlx5e_vport_rep_unload+0x184/0x1b8 [mlx5_core] mlx5_esw_offloads_rep_load+0xd8/0xe0 [mlx5_core] mlx5_eswitch_reload_reps+0x74/0xd0 [mlx5_core] mlx5_disable_lag+0x130/0x138 [mlx5_core] mlx5_lag_disable_change+0x6c/0x70 [mlx5_core] // hold ldev->lock mlx5_devlink_eswitch_mode_set+0xc0/0x410 [mlx5_core] devlink_nl_cmd_eswitch_set_doit+0xdc/0x180 genl_family_rcv_msg_doit.isra.17+0xe8/0x138 genl_rcv_msg+0xe4/0x220 netlink_rcv_skb+0x44/0x108 genl_rcv+0x40/0x58 netlink_unicast+0x198/0x268 netlink_sendmsg+0x1d4/0x418 sock_sendmsg+0x54/0x60 __sys_sendto+0xf4/0x120 __arm64_sys_sendto+0x30/0x40 el0_svc_common+0x8c/0x120 do_el0_svc+0x30/0xa0 el0_svc+0x20/0x30 el0_sync_handler+0x90/0xb8 el0_sync+0x160/0x180 Thus, upon lag enable/disable, load and unload only the IB representors of the slaves preventing the deadlock mentioned above. While at it, refactor the mlx5_esw_offloads_rep_load() function to have a static helper method for its internal logic, in symmetry with the representor unload design.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock systems using the mlx5 network driver when link aggregation is enabled or disabled under specific representor failure conditions. The likely impact is availability disruption, not data theft. Exposure appears limited to environments using mlx5 hardware and advanced networking features such as LAG, eswitch, and IB representors.

Executive priority

Treat as a targeted availability risk for specialized network infrastructure. Patch affected mlx5-enabled Linux hosts during the next appropriate maintenance window, sooner where these hosts support critical virtualization, storage, or network services.

Technical view

The mlx5 LAG disable path held the LAG lock, then an error path could unload Ethernet representors and re-enter LAG netdev removal, requiring the same lock and causing deadlock. The resolved change limits LAG enable/disable reload behavior to slave IB representors and refactors representor load handling.

Likely exposure

Most exposed systems are Linux hosts with mlx5_core and Mellanox/NVIDIA mlx5 adapters using LAG plus eswitch/offload representor workflows. General Linux systems without mlx5 hardware or these networking modes are unlikely to be affected based on the provided record.

Exploitation context

The source bundle does not show active exploitation, public weaponization, or KEV listing. Triggering appears tied to privileged networking control paths such as devlink eswitch mode changes and driver state transitions, with the primary observed result being kernel deadlock.

Researcher notes

Evidence is strongest for a kernel-driver deadlock and narrow configuration dependency. CVSS, CWE, and severity are not provided in the bundle. The affected version data is sparse, so distribution advisories should determine exact package exposure and fixed builds.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Prioritize hosts using mlx5 LAG, eswitch offloads, and IB representors.
  • Check vendor or distribution kernel advisories for backported fixes.
  • Avoid unnecessary LAG enable or disable operations on exposed mlx5 hosts until patched.

Validation and detection

  • Inventory Linux systems using mlx5_core and mlx5 network adapters.
  • Identify hosts using LAG with eswitch or representor functionality.
  • Compare running kernel builds against vendor fixed package guidance.
  • Review kernel logs for mlx5 LAG, representor reload, or deadlock symptoms.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-38557 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux598fe77df855feeeca9dfda2ffe622ac7724e5c3, 598fe77df855feeeca9dfda2ffe622ac7724e5c3, 598fe77df855feeeca9dfda2ffe622ac7724e5c3, 598fe77df855feeeca9dfda2ffe622ac7724e5c3unaffected
LinuxLinux5.15, 0, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.