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

The remote Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5818 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5818-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     November 24, 2024                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2022-45888 CVE-2023-52812 CVE-2024-26952 CVE-2024-26954                      CVE-2024-35964 CVE-2024-36244 CVE-2024-36478 CVE-2024-36914                      CVE-2024-36915 CVE-2024-36923 CVE-2024-38540 CVE-2024-38553                      CVE-2024-41080 CVE-2024-42322 CVE-2024-43868 CVE-2024-43904                      CVE-2024-43911 CVE-2024-44949 CVE-2024-49950 CVE-2024-49960                      CVE-2024-49974 CVE-2024-49986 CVE-2024-49991 CVE-2024-50012                      CVE-2024-50036 CVE-2024-50067 CVE-2024-50072 CVE-2024-50126                      CVE-2024-50215 CVE-2024-50218 CVE-2024-50228 CVE-2024-50229                      CVE-2024-50230 CVE-2024-50232 CVE-2024-50233 CVE-2024-50234                      CVE-2024-50235 CVE-2024-50236 CVE-2024-50237 CVE-2024-50242                      CVE-2024-50243 CVE-2024-50244 CVE-2024-50245 CVE-2024-50247                      CVE-2024-50249 CVE-2024-50250 CVE-2024-50251 CVE-2024-50252                      CVE-2024-50255 CVE-2024-50256 CVE-2024-50257 CVE-2024-50259                      CVE-2024-50261 CVE-2024-50262 CVE-2024-50264 CVE-2024-50265                      CVE-2024-50267 CVE-2024-50268 CVE-2024-50269 CVE-2024-50271                      CVE-2024-50272 CVE-2024-50273 CVE-2024-50276 CVE-2024-50278                      CVE-2024-50279 CVE-2024-50280 CVE-2024-50282 CVE-2024-50283                      CVE-2024-50284 CVE-2024-50286 CVE-2024-50287 CVE-2024-50290                      CVE-2024-50292 CVE-2024-50295 CVE-2024-50296 CVE-2024-50299                      CVE-2024-50301 CVE-2024-50302 CVE-2024-53042 CVE-2024-53043                      CVE-2024-53052 CVE-2024-53054 CVE-2024-53055 CVE-2024-53057                      CVE-2024-53058 CVE-2024-53059 CVE-2024-53060 CVE-2024-53061                      CVE-2024-53063 CVE-2024-53066 CVE-2024-53070 CVE-2024-53072                      CVE-2024-53081 CVE-2024-53082 CVE-2024-53088 CVE-2024-53093

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the stable distribution (bookworm), these problems have been fixed in     version 6.1.119-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

CVE-2024-53058

medium

Tenable Plugins

high