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

CVE-2024-44984

A critical vulnerability in the Linux kernel's bnxt_en network driver causes a double DMA unmapping error when processing XDP_REDIRECT packets, triggering a kernel warning and potentially leading to instability. The flaw has been assigned a CVSS base score of 10 (critical). The issue is resolved by removing the erroneous dma_unmap_page_attrs() call, and a fix is included in the Linux kernel source.

publishedSep 4, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
10
critical · how bad it is
exploitation · epss
<1%
14th 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

Linux kernel systems using the bnxt_en driver (including versions referenced in the CPE data).

02

Real-world impact

Exploitation could lead to kernel warnings, possible denial of service, or other unpredictable behavior due to improper DMA handling.

03

Why this severity

The CVSS score of 10 reflects the vulnerability's network‑adjacent, low‑complexity nature with no privileges or user interaction required, and its potential to affect confidentiality, integrity, and availability.

04

What to do about it

official fix available
recommended steps
  1. 011. Obtain a Linux kernel version that includes the bnxt_en fix for CVE-2024-44984 (the patch that removes the dma_unmap_page_attrs() call in the XDP_REDIRECT code path).
  2. 022. Install the updated kernel on the affected system.
  3. 033. Reboot the system to load the patched kernel.

NVD-referenced vendor advisory (the NVD description states the vulnerability has been resolved in the Linux kernel).

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
ScopeChanged
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 →