LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35959: net/mlx5e: Fix mlx5e_priv_init() cleanup flow

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix mlx5e_priv_init() cleanup flow When mlx5e_priv_init() fails, the cleanup flow calls mlx5e_selq_cleanup which calls mlx5e_selq_apply() that assures that the `priv->state_lock` is held using lockdep_is_held(). Acquire the state_lock in mlx5e_selq_cleanup(). Kernel log: ============================= WARNING: suspicious RCU usage 6.8.0-rc3_net_next_841a9b5 #1 Not tainted ----------------------------- drivers/net/ethernet/mellanox/mlx5/core/en/selq.c:124 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 2 locks held by systemd-modules/293: #0: ffffffffa05067b0 (devices_rwsem){++++}-{3:3}, at: ib_register_client+0x109/0x1b0 [ib_core] #1: ffff8881096c65c0 (&device->client_data_rwsem){++++}-{3:3}, at: add_client_context+0x104/0x1c0 [ib_core] stack backtrace: CPU: 4 PID: 293 Comm: systemd-modules Not tainted 6.8.0-rc3_net_next_841a9b5 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x8a/0xa0 lockdep_rcu_suspicious+0x154/0x1a0 mlx5e_selq_apply+0x94/0xa0 [mlx5_core] mlx5e_selq_cleanup+0x3a/0x60 [mlx5_core] mlx5e_priv_init+0x2be/0x2f0 [mlx5_core] mlx5_rdma_setup_rn+0x7c/0x1a0 [mlx5_core] rdma_init_netdev+0x4e/0x80 [ib_core] ? mlx5_rdma_netdev_free+0x70/0x70 [mlx5_core] ipoib_intf_init+0x64/0x550 [ib_ipoib] ipoib_intf_alloc+0x4e/0xc0 [ib_ipoib] ipoib_add_one+0xb0/0x360 [ib_ipoib] add_client_context+0x112/0x1c0 [ib_core] ib_register_client+0x166/0x1b0 [ib_core] ? 0xffffffffa0573000 ipoib_init_module+0xeb/0x1a0 [ib_ipoib] do_one_initcall+0x61/0x250 do_init_module+0x8a/0x270 init_module_from_file+0x8b/0xd0 idempotent_init_module+0x17d/0x230 __x64_sys_finit_module+0x61/0xb0 do_syscall_64+0x71/0x140 entry_SYSCALL_64_after_hwframe+0x46/0x4e </TASK>

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Mellanox mlx5 networking code during a failed driver initialization cleanup path. The available record shows a locking/RCU correctness bug that can trigger a kernel warning. Business urgency depends on whether affected kernels and mlx5 hardware or drivers are present.

Executive priority

Set priority after asset scoping. If mlx5-enabled Linux infrastructure is common or business-critical, handle in the next kernel patch cycle. Without affected hardware or driver use, urgency is lower, but confirm through inventory rather than assumption.

Technical view

mlx5e_priv_init() failure cleanup calls mlx5e_selq_cleanup(), which calls mlx5e_selq_apply() without holding priv->state_lock. The fix acquires state_lock in mlx5e_selq_cleanup() to satisfy protected RCU access expectations. The source bundle does not provide CVSS, CWE, or a concrete security impact beyond the kernel warning trace.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions or commits with the Mellanox mlx5 Ethernet/RDMA driver path in use. Validate against installed kernel builds and distribution backports, because the source bundle lists upstream stable references but not vendor package names.

Exploitation context

No active exploitation is stated. The CVE is not listed as KEV in the supplied bundle, and no cited source describes public exploitation, exploit prerequisites, or weaponized use. Treat this as a kernel maintenance and reliability concern unless vendor guidance says otherwise.

Researcher notes

Evidence is incomplete for exploitability and impact. The record describes a missing lock around RCU-protected cleanup logic, fixed by taking state_lock. Focus analysis on affected kernel lineage, mlx5e initialization failure paths, and whether downstream vendors backported the referenced commits.

Mitigation direction

  • Check Linux vendor advisories for patched kernel packages containing the referenced stable fixes.
  • Prioritize systems using Mellanox mlx5 Ethernet or RDMA drivers.
  • Update affected kernels through normal vendor-supported kernel channels.
  • Plan maintenance windows for hosts requiring kernel reboot or driver reload.
  • Monitor kernel logs for related mlx5e, RCU, or lockdep warnings.

Validation and detection

  • Inventory kernel versions and Mellanox mlx5 driver usage across Linux hosts.
  • Compare deployed kernels with vendor-fixed packages and upstream stable references.
  • Review dmesg or centralized logs for the cited suspicious RCU warning pattern.
  • Confirm patched systems boot the intended kernel after maintenance.
  • Document any distribution backport evidence used for closure.
Prepared
Confidence
medium
Sources
6

Public sources used

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-35959 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8bf30be75069d6080659de9a28565c048f6cef9b, 8bf30be75069d6080659de9a28565c048f6cef9b, 8bf30be75069d6080659de9a28565c048f6cef9b, 8bf30be75069d6080659de9a28565c048f6cef9bunaffected
LinuxLinux5.18, 0, 6.1.87, 6.6.28, 6.8.7, 6.9affected
Weakness

CWE details

No CWE listed

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