CVE-2022-49338

/// Technical description

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

net/mlx5e: CT: Fix cleanup of CT before cleanup of TC ct rules

CT cleanup assumes that all tc rules were deleted first, and so

is free to delete the CT shared resources (e.g the dr_action

fwd_action which is shared for all tuples). But currently for

uplink, this is happens in reverse, causing the below trace.

CT cleanup is called from:

mlx5e_cleanup_rep_tx()->mlx5e_cleanup_uplink_rep_tx()->

mlx5e_rep_tc_cleanup()->mlx5e_tc_esw_cleanup()->

mlx5_tc_ct_clean()

Only afterwards, tc cleanup is called from:

mlx5e_cleanup_rep_tx()->mlx5e_tc_ht_cleanup()

which would have deleted all the tc ct rules, and so delete

all the offloaded tuples.

Fix this reversing the order of init and on cleanup, which

will result in tc cleanup then ct cleanup.

[ 9443.593347] WARNING: CPU: 2 PID: 206774 at drivers/net/ethernet/mellanox/mlx5/core/steering/dr_action.c:1882 mlx5dr_action_destroy+0x188/0x1a0 [mlx5_core]

[ 9443.593349] Modules linke

/// 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