From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - Title: net/mlx5e: Don't call cleanup on profile rollback failure - Description: When profile rollback fails, the netdev var in mlx5e_netdev_change_profile is set to NULL. Avoid calling profile->cleanup during driver unload in this case to prevent crashes. 2. Trigger Conditions: - During testing, the trigger condition was the interruption of wq rescuer thread creation (possibly due to Ctrl+C-ing modprobe), resulting in an ENOMEM (-12) error. - mlx5e_priv_init's profile rollback also failed because the signal was still active, causing the profile to be set to NULL, which later led to a crash in _mlx5e_remove. 3. Fixes: - Fixed by commit 3ef14e463f6e ("net/mlx5e: Separate between netdev objects and mlx5e profiles initialization"). - Modified code in _call_trace to avoid calling profile->cleanup when profile rollback fails. 4. Authors and Reviewers: - Author: Cosmin Ratiu - Reviewers: Dragos Tatulea , Tariq Toukan , Paolo Abeni 5. Diffstat: - 1 file changed, 3 insertions, 1 deletion. 6. Code Changes: - Removed the profile->cleanup call in _mlx5e_remove and added a conditional check to prevent calling profile->cleanup when profile rollback fails. This information indicates that the vulnerability is related to abnormal behavior in the mlx5e driver when profile rollback fails. The fix primarily involves avoiding unnecessary cleanup operations in such scenarios.