← Back to browse · API

CVE-2024-56719

Severity
CRITICAL
CVSS
10.0
EPSS
0.00496
Risk score
40.17
CISA KEV
No
PoC
Yes
Published
2024-12-29
Modified
2026-08-05
First seen
2026-08-05
Aliases
EUVD-2024-53367, GHSA-3868-3WH9-6QR7
Products
Linux:Linux 07c9c26e37542486e34d767505e842f48f29c3f6 <db3667c9bbfbbf5de98e6c9542f7e03fb5243286, Linux:Linux 5.15.171 <5.15.209, Linux:Linux 58d23d835eb498336716cca55b5714191a309286, Linux:Linux 6.1.116 <6.1.167, Linux:Linux 6.11.7 <6.12, Linux:Linux 6.12, Linux:Linux 6.6.60 <6.6.68, Linux:Linux 66600fac7a984dea4ae095411f644770b2561ede <4c49f38e20a57f8abaebdf95b369295b153d1f8e, Linux:Linux 66600fac7a984dea4ae095411f644770b2561ede <9d5dd7ccea1b46a9a7c6b3c2b9e5ed8864e185e2, Linux:Linux a3ff23f7c3f0e13f718900803e090fd3997d6bc9 <6abcdc9a73274052a9e96a1926994ecf9aedad82, Linux:Linux ece593fc9c00741b682869d3f3dc584d37b7c9df <05968b6dd0ffc65d7386608b11a11fb4fdfc9f36, Linux:Linux patch: 0, Linux:Linux patch: 5.15.209, Linux:Linux patch: 6.1.167, Linux:Linux patch: 6.12.7, Linux:Linux patch: 6.13, Linux:Linux patch: 6.6.68, debian, linux, linux:linux_kernel, ubuntu
Sources
packetstorm 707d837b18f57c6e8f884fba|CVE-2024-56719
packetstorm c3b1a20d39b7b74e47e665af|CVE-2024-56719
packetstorm 899dba7cbcf992a18f17c397|CVE-2024-56719
packetstorm 9e8699cec66acbdf41b03754|CVE-2024-56719
packetstorm e63b1d1b4ea43c3ae3f9dab6|CVE-2024-56719
packetstorm 6866beb4c5fa740fad3b91fb|CVE-2024-56719
packetstorm b5713193dd95eb648bef8a5d|CVE-2024-56719
packetstorm b2250ee24a4de63ce0943a8f|CVE-2024-56719
packetstorm 3acb901dfe19a3f4b90d11b0|CVE-2024-56719
nvd CVE-2024-56719
packetstorm 33a68b928098f160ab1797d7|CVE-2024-56719
packetstorm d08951b59bdd9795a5e84496|CVE-2024-56719
euvd EUVD-2024-53367
packetstorm 2a2c7b7113beffc2662be0f6|CVE-2024-56719

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/d8112193-0386-4e14-b516-37c2d838171a@nvidia.com/ https://lore.kernel.org/all/klkzp5yn5kq5efgtrow6wbvnc46bcqfxs65nz3qy77ujr5turc@bwwhelz2l4dw/

References