Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2024-44970

A critical flaw in the Linux kernel’s mlx5e driver can corrupt the work queue linked list when a work queue element is unlinked twice. This can lead to memory corruption and potentially allow an attacker to crash or take control of the system. The issue has been fixed in a recent kernel update.

publishedSep 4, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
11th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

All Linux kernel users that run a kernel with the mlx5e driver before the fix, especially those using Mellanox (now NVIDIA) network adapters that rely on the mlx5e driver.

02

Real-world impact

An attacker could send specially crafted completion queue entries that trigger the double unlink, causing memory corruption. This could lead to a denial‑of‑service or, in some cases, arbitrary code execution on the affected system.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited remotely with no authentication or user interaction, and it can compromise confidentiality, integrity, and availability. The high impact and ease of exploitation justify the critical rating.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel to a version that includes the fix for CVE-2024-44970.
  2. 02Reboot the system to load the new kernel.

NVD description indicates the vulnerability has been resolved

05

Timeline

  1. Sep 4, 2024 · Sep 4, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →