CVE-2024-53058 (GCVE-0-2024-53058)
Vulnerability from cvelistv5
Published
2024-11-19 17:19
Modified
2026-08-05 11:43
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data In case the non-paged data of a SKB carries protocol header and protocol payload to be transmitted on a certain platform that the DMA AXI address width is configured to 40-bit/48-bit, or the size of the non-paged data is bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI address width is configured to 32-bit, then this SKB requires at least two DMA transmit descriptors to serve it. For example, three descriptors are allocated to split one DMA buffer mapped from one piece of non-paged data: dma_desc[N + 0], dma_desc[N + 1], dma_desc[N + 2]. Then three elements of tx_q->tx_skbuff_dma[] will be allocated to hold extra information to be reused in stmmac_tx_clean(): tx_q->tx_skbuff_dma[N + 0], tx_q->tx_skbuff_dma[N + 1], tx_q->tx_skbuff_dma[N + 2]. Now we focus on tx_q->tx_skbuff_dma[entry].buf, which is the DMA buffer address returned by DMA mapping call. stmmac_tx_clean() will try to unmap the DMA buffer _ONLY_IF_ tx_q->tx_skbuff_dma[entry].buf is a valid buffer address. The expected behavior that saves DMA buffer address of this non-paged data to tx_q->tx_skbuff_dma[entry].buf is: tx_q->tx_skbuff_dma[N + 0].buf = NULL; tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = dma_map_single(); Unfortunately, the current code misbehaves like this: tx_q->tx_skbuff_dma[N + 0].buf = dma_map_single(); tx_q->tx_skbuff_dma[N + 1].buf = NULL; tx_q->tx_skbuff_dma[N + 2].buf = NULL; On the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the DMA engine, tx_q->tx_skbuff_dma[N + 0].buf is a valid buffer address obviously, then the DMA buffer will be unmapped immediately. There may be a rare case that the DMA engine does not finish the pending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go horribly wrong, DMA is going to access a unmapped/unreferenced memory region, corrupted data will be transmited or iommu fault will be triggered :( In contrast, the for-loop that maps SKB fragments behaves perfectly as expected, and that is how the driver should do for both non-paged data and paged frags actually. This patch corrects DMA map/unmap sequences by fixing the array index for tx_q->tx_skbuff_dma[entry].buf when assigning DMA buffer address. Tested and verified on DWXGMAC CORE 3.20a
Impacted products
Vendor Product Version
Linux Linux Version: f748be531d7012c456b97f66091d86b3675c5fef
Version: f748be531d7012c456b97f66091d86b3675c5fef
Version: f748be531d7012c456b97f66091d86b3675c5fef
Version: f748be531d7012c456b97f66091d86b3675c5fef
Version: f748be531d7012c456b97f66091d86b3675c5fef
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-53058",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:12:56.492428Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "description": "CWE-noinfo Not enough information",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:17:17.845Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T22:28:51.972Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ece593fc9c00741b682869d3f3dc584d37b7c9df",
              "status": "affected",
              "version": "f748be531d7012c456b97f66091d86b3675c5fef",
              "versionType": "git"
            },
            {
              "lessThan": "a3ff23f7c3f0e13f718900803e090fd3997d6bc9",
              "status": "affected",
              "version": "f748be531d7012c456b97f66091d86b3675c5fef",
              "versionType": "git"
            },
            {
              "lessThan": "07c9c26e37542486e34d767505e842f48f29c3f6",
              "status": "affected",
              "version": "f748be531d7012c456b97f66091d86b3675c5fef",
              "versionType": "git"
            },
            {
              "lessThan": "58d23d835eb498336716cca55b5714191a309286",
              "status": "affected",
              "version": "f748be531d7012c456b97f66091d86b3675c5fef",
              "versionType": "git"
            },
            {
              "lessThan": "66600fac7a984dea4ae095411f644770b2561ede",
              "status": "affected",
              "version": "f748be531d7012c456b97f66091d86b3675c5fef",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.7"
            },
            {
              "lessThan": "4.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.171",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.116",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.60",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.171",
                  "versionStartIncluding": "4.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.116",
                  "versionStartIncluding": "4.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.60",
                  "versionStartIncluding": "4.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.7",
                  "versionStartIncluding": "4.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "4.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data\n\nIn case the non-paged data of a SKB carries protocol header and protocol\npayload to be transmitted on a certain platform that the DMA AXI address\nwidth is configured to 40-bit/48-bit, or the size of the non-paged data\nis bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI\naddress width is configured to 32-bit, then this SKB requires at least\ntwo DMA transmit descriptors to serve it.\n\nFor example, three descriptors are allocated to split one DMA buffer\nmapped from one piece of non-paged data:\n    dma_desc[N + 0],\n    dma_desc[N + 1],\n    dma_desc[N + 2].\nThen three elements of tx_q-\u003etx_skbuff_dma[] will be allocated to hold\nextra information to be reused in stmmac_tx_clean():\n    tx_q-\u003etx_skbuff_dma[N + 0],\n    tx_q-\u003etx_skbuff_dma[N + 1],\n    tx_q-\u003etx_skbuff_dma[N + 2].\nNow we focus on tx_q-\u003etx_skbuff_dma[entry].buf, which is the DMA buffer\naddress returned by DMA mapping call. stmmac_tx_clean() will try to\nunmap the DMA buffer _ONLY_IF_ tx_q-\u003etx_skbuff_dma[entry].buf\nis a valid buffer address.\n\nThe expected behavior that saves DMA buffer address of this non-paged\ndata to tx_q-\u003etx_skbuff_dma[entry].buf is:\n    tx_q-\u003etx_skbuff_dma[N + 0].buf = NULL;\n    tx_q-\u003etx_skbuff_dma[N + 1].buf = NULL;\n    tx_q-\u003etx_skbuff_dma[N + 2].buf = dma_map_single();\nUnfortunately, the current code misbehaves like this:\n    tx_q-\u003etx_skbuff_dma[N + 0].buf = dma_map_single();\n    tx_q-\u003etx_skbuff_dma[N + 1].buf = NULL;\n    tx_q-\u003etx_skbuff_dma[N + 2].buf = NULL;\n\nOn the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the\nDMA engine, tx_q-\u003etx_skbuff_dma[N + 0].buf is a valid buffer address\nobviously, then the DMA buffer will be unmapped immediately.\nThere may be a rare case that the DMA engine does not finish the\npending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go\nhorribly wrong, DMA is going to access a unmapped/unreferenced memory\nregion, corrupted data will be transmited or iommu fault will be\ntriggered :(\n\nIn contrast, the for-loop that maps SKB fragments behaves perfectly\nas expected, and that is how the driver should do for both non-paged\ndata and paged frags actually.\n\nThis patch corrects DMA map/unmap sequences by fixing the array index\nfor tx_q-\u003etx_skbuff_dma[entry].buf when assigning DMA buffer address.\n\nTested and verified on DWXGMAC CORE 3.20a"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.4,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The vulnerable code is the stmmac TSO transmit path, driven directly by remote traffic \u2014 an unauthenticated peer pulling data from any service on the device, or forwarded/GRO-coalesced streams re-segmented on egress by an stmmac-based gateway, arm the bug, and the resulting corrupted frames (carrying recycled kernel memory) are delivered to that remote peer. The attacker set is not bounded to the local LAN or local machine.\nAC:L - On the common 40/48-bit AXI platforms the mismatched map/unmap occurs on essentially every TSO frame whose linear head carries payload, in the default configuration, and the attacker can drive that path at line rate without limit, so the DMA-completion window is hit repeatedly rather than requiring a skilled one-shot race win.\nPR:N - No authentication or privilege is needed \u2014 merely causing the host to transmit large TCP/UDP-GSO data (a plain TCP connection to any listening service, or traffic routed through the device) reaches the code; locally, an ordinary unprivileged socket send suffices.\nUI:N - Triggering requires only network traffic to or through the affected interface; no action by any local user or administrator is involved.\nS:U - The stale IOVA is recycled within the same device\u0027s own DMA domain and the impacted resources belong to the kernel that owns the driver, so no security authority boundary (VM, IOMMU domain, sandbox) is crossed.\nC:H - When the unmapped IOVA or SWIOTLB slot is reused before the engine finishes, the MAC reads whatever buffer now occupies it \u2014 other sockets\u0027 packet data, page-pool/page-frag pages, or another device\u0027s bounced I/O \u2014 and transmits it on the wire with valid hardware checksums, handing an unbounded amount of kernel memory straight to the remote peer.\nI:L - Outbound frame contents are silently replaced with unrelated memory and re-checksummed by hardware, so peers accept corrupted data undetected, but the device only performs DMA reads \u2014 there is no kernel write primitive and the attacker cannot control what gets corrupted.\nA:H - DMA to a torn-down mapping raises IOMMU translation faults and aborted transactions, producing TX errors, log floods, TX-watchdog-driven device resets and link loss, and on SoCs that escalate the resulting bus error an unrecoverable external abort."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:43:21.929Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ece593fc9c00741b682869d3f3dc584d37b7c9df"
        },
        {
          "url": "https://git.kernel.org/stable/c/a3ff23f7c3f0e13f718900803e090fd3997d6bc9"
        },
        {
          "url": "https://git.kernel.org/stable/c/07c9c26e37542486e34d767505e842f48f29c3f6"
        },
        {
          "url": "https://git.kernel.org/stable/c/58d23d835eb498336716cca55b5714191a309286"
        },
        {
          "url": "https://git.kernel.org/stable/c/66600fac7a984dea4ae095411f644770b2561ede"
        }
      ],
      "title": "net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53058",
    "datePublished": "2024-11-19T17:19:40.912Z",
    "dateReserved": "2024-11-19T17:17:24.974Z",
    "dateUpdated": "2026-08-05T11:43:21.929Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T22:28:51.972Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-53058\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T20:12:56.492428Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"description\": \"CWE-noinfo Not enough information\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:29:37.654Z\"}}], \"cna\": {\"title\": \"net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 9.4, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:N - The vulnerable code is the stmmac TSO transmit path, driven directly by remote traffic \\u2014 an unauthenticated peer pulling data from any service on the device, or forwarded/GRO-coalesced streams re-segmented on egress by an stmmac-based gateway, arm the bug, and the resulting corrupted frames (carrying recycled kernel memory) are delivered to that remote peer. The attacker set is not bounded to the local LAN or local machine.\\nAC:L - On the common 40/48-bit AXI platforms the mismatched map/unmap occurs on essentially every TSO frame whose linear head carries payload, in the default configuration, and the attacker can drive that path at line rate without limit, so the DMA-completion window is hit repeatedly rather than requiring a skilled one-shot race win.\\nPR:N - No authentication or privilege is needed \\u2014 merely causing the host to transmit large TCP/UDP-GSO data (a plain TCP connection to any listening service, or traffic routed through the device) reaches the code; locally, an ordinary unprivileged socket send suffices.\\nUI:N - Triggering requires only network traffic to or through the affected interface; no action by any local user or administrator is involved.\\nS:U - The stale IOVA is recycled within the same device\u0027s own DMA domain and the impacted resources belong to the kernel that owns the driver, so no security authority boundary (VM, IOMMU domain, sandbox) is crossed.\\nC:H - When the unmapped IOVA or SWIOTLB slot is reused before the engine finishes, the MAC reads whatever buffer now occupies it \\u2014 other sockets\u0027 packet data, page-pool/page-frag pages, or another device\u0027s bounced I/O \\u2014 and transmits it on the wire with valid hardware checksums, handing an unbounded amount of kernel memory straight to the remote peer.\\nI:L - Outbound frame contents are silently replaced with unrelated memory and re-checksummed by hardware, so peers accept corrupted data undetected, but the device only performs DMA reads \\u2014 there is no kernel write primitive and the attacker cannot control what gets corrupted.\\nA:H - DMA to a torn-down mapping raises IOMMU translation faults and aborted transactions, producing TX errors, log floods, TX-watchdog-driven device resets and link loss, and on SoCs that escalate the resulting bus error an unrecoverable external abort.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"f748be531d7012c456b97f66091d86b3675c5fef\", \"lessThan\": \"ece593fc9c00741b682869d3f3dc584d37b7c9df\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f748be531d7012c456b97f66091d86b3675c5fef\", \"lessThan\": \"a3ff23f7c3f0e13f718900803e090fd3997d6bc9\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f748be531d7012c456b97f66091d86b3675c5fef\", \"lessThan\": \"07c9c26e37542486e34d767505e842f48f29c3f6\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f748be531d7012c456b97f66091d86b3675c5fef\", \"lessThan\": \"58d23d835eb498336716cca55b5714191a309286\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f748be531d7012c456b97f66091d86b3675c5fef\", \"lessThan\": \"66600fac7a984dea4ae095411f644770b2561ede\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/net/ethernet/stmicro/stmmac/stmmac_main.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.7\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"4.7\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.171\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"6.1.116\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.60\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.7\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/net/ethernet/stmicro/stmmac/stmmac_main.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/ece593fc9c00741b682869d3f3dc584d37b7c9df\"}, {\"url\": \"https://git.kernel.org/stable/c/a3ff23f7c3f0e13f718900803e090fd3997d6bc9\"}, {\"url\": \"https://git.kernel.org/stable/c/07c9c26e37542486e34d767505e842f48f29c3f6\"}, {\"url\": \"https://git.kernel.org/stable/c/58d23d835eb498336716cca55b5714191a309286\"}, {\"url\": \"https://git.kernel.org/stable/c/66600fac7a984dea4ae095411f644770b2561ede\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data\\n\\nIn case the non-paged data of a SKB carries protocol header and protocol\\npayload to be transmitted on a certain platform that the DMA AXI address\\nwidth is configured to 40-bit/48-bit, or the size of the non-paged data\\nis bigger than TSO_MAX_BUFF_SIZE on a certain platform that the DMA AXI\\naddress width is configured to 32-bit, then this SKB requires at least\\ntwo DMA transmit descriptors to serve it.\\n\\nFor example, three descriptors are allocated to split one DMA buffer\\nmapped from one piece of non-paged data:\\n    dma_desc[N + 0],\\n    dma_desc[N + 1],\\n    dma_desc[N + 2].\\nThen three elements of tx_q-\u003etx_skbuff_dma[] will be allocated to hold\\nextra information to be reused in stmmac_tx_clean():\\n    tx_q-\u003etx_skbuff_dma[N + 0],\\n    tx_q-\u003etx_skbuff_dma[N + 1],\\n    tx_q-\u003etx_skbuff_dma[N + 2].\\nNow we focus on tx_q-\u003etx_skbuff_dma[entry].buf, which is the DMA buffer\\naddress returned by DMA mapping call. stmmac_tx_clean() will try to\\nunmap the DMA buffer _ONLY_IF_ tx_q-\u003etx_skbuff_dma[entry].buf\\nis a valid buffer address.\\n\\nThe expected behavior that saves DMA buffer address of this non-paged\\ndata to tx_q-\u003etx_skbuff_dma[entry].buf is:\\n    tx_q-\u003etx_skbuff_dma[N + 0].buf = NULL;\\n    tx_q-\u003etx_skbuff_dma[N + 1].buf = NULL;\\n    tx_q-\u003etx_skbuff_dma[N + 2].buf = dma_map_single();\\nUnfortunately, the current code misbehaves like this:\\n    tx_q-\u003etx_skbuff_dma[N + 0].buf = dma_map_single();\\n    tx_q-\u003etx_skbuff_dma[N + 1].buf = NULL;\\n    tx_q-\u003etx_skbuff_dma[N + 2].buf = NULL;\\n\\nOn the stmmac_tx_clean() side, when dma_desc[N + 0] is closed by the\\nDMA engine, tx_q-\u003etx_skbuff_dma[N + 0].buf is a valid buffer address\\nobviously, then the DMA buffer will be unmapped immediately.\\nThere may be a rare case that the DMA engine does not finish the\\npending dma_desc[N + 1], dma_desc[N + 2] yet. Now things will go\\nhorribly wrong, DMA is going to access a unmapped/unreferenced memory\\nregion, corrupted data will be transmited or iommu fault will be\\ntriggered :(\\n\\nIn contrast, the for-loop that maps SKB fragments behaves perfectly\\nas expected, and that is how the driver should do for both non-paged\\ndata and paged frags actually.\\n\\nThis patch corrects DMA map/unmap sequences by fixing the array index\\nfor tx_q-\u003etx_skbuff_dma[entry].buf when assigning DMA buffer address.\\n\\nTested and verified on DWXGMAC CORE 3.20a\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.171\", \"versionStartIncluding\": \"4.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.116\", \"versionStartIncluding\": \"4.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.60\", \"versionStartIncluding\": \"4.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.7\", \"versionStartIncluding\": \"4.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"4.7\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:43:21.929Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-53058\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:43:21.929Z\", \"dateReserved\": \"2024-11-19T17:17:24.974Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-11-19T17:19:40.912Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…