LiveActive security incident?Get immediate response
CVE Record

CVE-2024-56719: net: stmmac: fix TSO DMA API usage causing oops

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/

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-56719 is a Linux kernel network-driver flaw that can crash affected systems. It involves the stmmac Ethernet driver mishandling DMA addresses during TSO transmit cleanup. The business risk is service availability, especially for embedded or industrial Linux devices using this driver.

Executive priority

Schedule remediation during the next maintenance cycle for exposed systems, sooner for critical networked embedded or industrial assets. This is not shown as actively exploited, but it can affect availability and should not be ignored where uptime matters.

Technical view

The stmmac TSO path stored an offset DMA cookie and later passed it to dma_unmap_single(), violating DMA API requirements. On systems with 64-bit DMA addressing above 32 bits, this can trigger DMA mapping errors, DMA_API_DEBUG reports, or kernel oops conditions.

Likely exposure

Exposure is most likely on Linux systems using the stmmac/DWMAC Ethernet driver with TSO enabled, including some embedded or industrial devices. Generic Linux servers not using this driver are less likely exposed. The bundle lists Linux kernel versions and Siemens advisories, but product-specific impact should be verified.

Exploitation context

The CVE has CVSS 5.5 with local attack vector, low privileges, no user interaction, and high availability impact. The source bundle does not show CISA KEV listing or active exploitation. Treat it as a stability and denial-of-service risk, not a confirmed exploited issue.

Researcher notes

The key condition is incorrect DMA cookie handling in stmmac_tso_xmit() after commit 66600fac7a98. Focus validation on driver presence, TSO path exposure, 64-bit DMA behavior, and whether downstream kernels have backported one of the stable fixes.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable stmmac fixes.
  • Check vendor advisories for affected Siemens or embedded products before deploying firmware updates.
  • Prioritize systems where network availability or industrial uptime is business-critical.
  • If no vendor patch is available, follow vendor guidance for temporary operational mitigations.

Validation and detection

  • Inventory Linux systems using the stmmac or DWMAC Ethernet driver.
  • Check running kernel versions against vendor and Linux stable advisories.
  • Review logs for stmmac Tx DMA map failures or DMA_API_DEBUG warnings.
  • Confirm patched systems include the referenced stable kernel commits.
  • Validate network stability after kernel or firmware updates in a test window.
Prepared
Confidence
high
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-56719 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-56719Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxece593fc9c00741b682869d3f3dc584d37b7c9df, a3ff23f7c3f0e13f718900803e090fd3997d6bc9, 07c9c26e37542486e34d767505e842f48f29c3f6, 66600fac7a984dea4ae095411f644770b2561ede, 66600fac7a984dea4ae095411f644770b2561ede, 58d23d835eb498336716cca55b5714191a309286, 5.15.171, 6.1.116, 6.6.60, 6.11.7unaffected
LinuxLinux6.12, 0, 5.15.209, 6.1.167, 6.6.68, 6.12.7, 6.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.