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

CVE-2024-53058

A bug in the Linux kernel’s STMMAC network driver caused incorrect DMA mapping for large packets, which could lead to memory corruption or system crashes. The issue occurs when the driver mismanages DMA buffer addresses for non‑paged packet data, potentially allowing an attacker to trigger a fault or corrupt transmitted data. The vulnerability has been fixed in the kernel.

publishedNov 19, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.4
critical · how bad it is
exploitation · epss
<1%
16th 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 3, 2026

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

01

Who is affected

Linux kernel 6.12 and earlier versions that use the STMMAC driver for Ethernet hardware. Typical users include Linux system administrators and embedded device developers.

02

Real-world impact

An attacker could cause a denial of service by triggering a memory fault or corrupting data transmission, potentially leading to system crashes or compromised network integrity.

03

Why this severity

The CVSS score of 9.4 reflects the high impact on confidentiality, integrity, and availability, combined with the fact that the vulnerability can be exploited remotely with no authentication or user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the fix for CVE-2024-53058 (e.g., the latest 6.12.x release).
  2. 02Reboot the system to load the updated kernel.

NVD description indicates the vulnerability has been resolved in the Linux kernel.

05

Timeline

  1. Nov 19, 2024 · Nov 19, 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 4, 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 impactLow
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 →