CVE-2026-53229

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure<br /> <br /> In the XSK branch of mlx5e_xmit_xdp_buff(), when sq-&gt;xmit_xdp_frame()<br /> returns false (e.g. XDPSQ is full), the function returns without<br /> unmapping the DMA address or freeing the xdp_frame allocated by<br /> xdp_convert_zc_to_xdp_frame(). The xdpi_fifo push only happens on<br /> success, so the completion path cannot recover these entries.<br /> <br /> With CONFIG_DMA_API_DEBUG=y, the leak surfaces on driver unbind:<br /> <br /> DMA-API: pci 0000:08:00.0: device driver has pending DMA<br /> allocations while released from device [count=1116]<br /> One of leaked entries details: [device address=0x000000010ffd7028]<br /> [size=1534 bytes] [mapped with DMA_TO_DEVICE] [mapped as phy]<br /> WARNING: kernel/dma/debug.c:881 at dma_debug_device_change+0x127/0x180<br /> ...<br /> DMA-API: Mapped at:<br /> debug_dma_map_phys+0x4b/0xd0<br /> dma_map_phys+0xfd/0x2d0<br /> mlx5e_xdp_handle+0x5ae/0xac0 [mlx5_core]<br /> mlx5e_xsk_skb_from_cqe_mpwrq_linear+0xc4/0x170 [mlx5_core]<br /> mlx5e_handle_rx_cqe_mpwrq+0xc1/0x290 [mlx5_core]<br /> <br /> Add the missing unmap + xdp_return_frame, matching the cleanup already<br /> done in mlx5e_xdp_xmit(). has_frags is rejected earlier in this branch,<br /> so no per-frag unmap is needed.