CVE-2025-38042

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: ti: k3-udma-glue: Drop skip_fdq argument from k3_udma_glue_reset_rx_chn

The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can

run on multiple platforms having different DMA architectures.

On some platforms there can be one FDQ for all flows in the RX channel

while for others there is a separate FDQ for each flow in the RX channel.

So far we have been relying on the skip_fdq argument of

k3_udma_glue_reset_rx_chn().

Instead of relying on the user to provide this information, infer it

based on DMA architecture during k3_udma_glue_request_rx_chn() and save it

in an internal flag 'single_fdq'. Use that flag at

k3_udma_glue_reset_rx_chn() to deicide if the FDQ needs

to be cleared for every flow or just for flow 0.

Fixes the below issue on ti_am65_cpsw_nuss driver on AM62-SK.

> ip link set eth1 down

> ip link set eth0 down

> ethtool -L eth0 rx 8

> ip link set eth0 up

> modprobe -r ti_am65_cpsw_nu

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References