CVE-2024-53209
The Linux kernel's bnxt_en network driver can corrupt memory and MTU is changed while XDP multi‑attached. This occurs because the aggregation ring configuration can become out‑of‑sync when the MTU is changed while XDP is active, leading to random memory corruption and system crashes. This flaw has been resolved by updating the receive ring settings whenever the MTU changes. Updating the kernel to a version that includes this fix removes the vulnerability.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
Systems running the Linux kernel with the bnxt_en driver (e.g., servers using Broadcom NetXtreme-E network adapters).
Real-world impact
An attacker who can trigger an MTU change (or who already has local access) could cause the kernel to crash or potentially execute arbitrary code, resulting in denial of service or privilege escalation.
Why this severity
The CVSS v3.1 base score is 9.8 (Critical) because the vulnerability is network‑reachable, requires no privileges or user interaction, and can lead to full compromise of confidentiality, integrity, and availability.
What to do about it
- 01Obtain the latest Linux kernel update from your distribution that includes the commit fixing bnxt_en receive ring space parameters when XDP is active.
- 02Install or upgrade the kernel package.
- 03Reboot the system to load the updated kernel.
NVD-referenced vendor advisory (Linux kernel fix)
Timeline
- Dec 27, 2024 · Dec 27, 2024PublishedDisclosed and added to the National Vulnerability Database.
- Aug 4, 2026 · 2d agoAdvisory updatedThe NVD record was last revised.
- Aug 4, 2026 · 1d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.