CVE-2024-56719

net: stmmac: fix TSO DMA API usage causing oops

MEDIUM
5.5
CVSS Score
Published: December 29, 2024 at 08:48 AM UTC
Updated: October 15, 2026 at 02:17 AM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: stmmac: fix TSO DMA API usage causing oops Commit 66600fac7a98 ("net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data") moved the assignment of tx_skbuff_dma[]'s members to be later in stmmac_tso_xmit(). The buf (dma cookie) and len stored in this structure are passed to dma_unmap_single() by stmmac_tx_clean(). The DMA API requires that the dma cookie passed to dma_unmap_single() is the same as the value returned from dma_map_single(). However, by moving the assignment later, this is not the case when priv->dma_cap.addr64 > 32 as "des" is offset by proto_hdr_len. This causes problems such as: dwc-eth-dwmac 2490000.ethernet eth0: Tx DMA map failed and with DMA_API_DEBUG enabled: DMA-API: dwc-eth-dwmac 2490000.ethernet: device driver tries to +free DMA memory it has not allocated [device address=0x000000ffffcf65c0] [size=66 bytes] Fix this by maintaining "des" as the original DMA cookie, and use tso_des to pass the offset DMA cookie to stmmac_tso_allocator(). Full details of the crashes can be found at: https://lore.kernel.org/all/[email protected]/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.171 ≤ v < 5.166.1.116 ≤ v < 6.26.11.7 ≤ v < 6.12.76.6.60 ≤ v < 6.6.685.15.17158d23d835eb498336716cca55b5714191a3092866.1.1166.11.76.136.13 rc16.13 rc26.6.6066600fac7a984dea4ae095411f644770b2561ede7c9c26e37542486e34d767505e842f48f29c3f6a3ff23f7c3f0e13f718900803e090fd3997d6bc9ece593fc9c00741b682869d3f3dc584d37b7c9df
Vendor states this is fixed in 05968b6dd0ffc65d7386608b11a11fb4fdfc9f36 (fixed)
Vendor states this is fixed in 4c49f38e20a57f8abaebdf95b369295b153d1f8e (fixed)
Vendor states this is fixed in 6abcdc9a73274052a9e96a1926994ecf9aedad82 (fixed)
Vendor states this is fixed in 9d5dd7ccea1b46a9a7c6b3c2b9e5ed8864e185e2 (fixed)
Vendor states this is fixed in db3667c9bbfbbf5de98e6c9542f7e03fb5243286 (fixed)
Vendor states this is fixed in 5.15.209 (unaffected)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.167 (unaffected)
Vendor states this is fixed in 6.12 (unaffected)
Vendor states this is fixed in 6.12.7 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.68 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card