LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35961: net/mlx5: Register devlink first under devlink lock

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Register devlink first under devlink lock In case device is having a non fatal FW error during probe, the driver will report the error to user via devlink. This will trigger a WARN_ON, since mlx5 is calling devlink_register() last. In order to avoid the WARN_ON[1], change mlx5 to invoke devl_register() first under devlink lock. [1] WARNING: CPU: 5 PID: 227 at net/devlink/health.c:483 devlink_recover_notify.constprop.0+0xb8/0xc0 CPU: 5 PID: 227 Comm: kworker/u16:3 Not tainted 6.4.0-rc5_for_upstream_min_debug_2023_06_12_12_38 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5_health0000:08:00.0 mlx5_fw_reporter_err_work [mlx5_core] RIP: 0010:devlink_recover_notify.constprop.0+0xb8/0xc0 Call Trace: <TASK> ? __warn+0x79/0x120 ? devlink_recover_notify.constprop.0+0xb8/0xc0 ? report_bug+0x17c/0x190 ? handle_bug+0x3c/0x60 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? devlink_recover_notify.constprop.0+0xb8/0xc0 devlink_health_report+0x4a/0x1c0 mlx5_fw_reporter_err_work+0xa4/0xd0 [mlx5_core] process_one_work+0x1bb/0x3c0 ? process_one_work+0x3c0/0x3c0 worker_thread+0x4d/0x3c0 ? process_one_work+0x3c0/0x3c0 kthread+0xc6/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-35961 is a Linux kernel mlx5 driver issue where a firmware health report during device startup can trigger a kernel warning because devlink was registered too late. The provided sources do not show data theft, privilege escalation, or remote exploitation. Business urgency depends on whether affected Linux kernels run mlx5 network hardware.

Executive priority

Handle through normal kernel maintenance unless affected mlx5 hosts are business-critical or showing kernel warnings. There is insufficient source evidence for emergency response, but infrastructure teams should confirm exposure because mlx5 hardware often sits on important network paths.

Technical view

The mlx5 driver could call devlink health reporting before devlink registration completed. During a non-fatal firmware error in probe, this ordering triggered WARN_ON in devlink_recover_notify. The fix registers devlink first under the devlink lock. The source lists Linux kernel affected versions and stable commit references, but no CVSS, CWE, or exploitability details.

Likely exposure

Exposure appears limited to Linux systems using the mlx5 driver, typically Mellanox/NVIDIA ConnectX-class networking, on affected kernel builds. Systems without mlx5 hardware or the mlx5_core driver are unlikely to be affected based on the supplied description.

Exploitation context

The bundle does not report active exploitation, and KEV is false. The described trigger is a non-fatal firmware error during device probe, not a documented attacker-controlled remote path. Treat exploitability and security impact as unproven from these sources.

Researcher notes

The useful research angle is impact clarification: whether WARN_ON is only diagnostic noise or can affect availability under common configurations. The CVE text names the ordering flaw and call trace, but omits CVSS, CWE, attack prerequisites, and distro-specific affected ranges.

Mitigation direction

  • Identify Linux systems using mlx5_core or mlx5-supported network adapters.
  • Apply distro or vendor kernel updates containing the referenced stable fixes.
  • Prioritize hosts where mlx5 adapters support production networking or storage fabrics.
  • Monitor kernel logs for mlx5, devlink, health reporter, or WARN_ON messages.
  • Check vendor advisories before applying non-distribution kernel patches.

Validation and detection

  • Confirm the running kernel version and distribution patch level.
  • Verify whether mlx5_core is loaded or mlx5 hardware is present.
  • Compare kernel source or package changelog against the referenced stable commits.
  • Review boot and kernel logs for devlink health WARN_ON traces.
  • Confirm updates in staging before production rollout.
Prepared
Confidence
medium
Sources
5

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-35961 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
4Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcf530217408e3686f7002429769ede59dd931151, cf530217408e3686f7002429769ede59dd931151, cf530217408e3686f7002429769ede59dd931151unaffected
LinuxLinux5.16, 0, 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.