AZL-69923

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

net/mlx5e: Fix cleanup null-ptr deref on encap lock

During module is unloaded while a peer tc flow is still offloaded, first the peer uplink rep profile is changed to a nic profile, and so neigh encap lock is destroyed. Next during unload, the VF reps netdevs are unregistered which causes the original non-peer tc flow to be deleted, which deletes the peer flow. The peer flow deletion detaches the encap entry and try to take the already destroyed encap lock, causing the below trace.

Fix this by clearing peer flows during tc eswitch cleanup (mlx5etcesw_cleanup()).

Relevant trace: [ 4316.837128] BUG: kernel NULL pointer dereference, address: 00000000000001d8 [ 4316.842239] RIP: 0010:__mutexlock+0xb5/0xc40 [ 4316.851897] Call Trace: [ 4316.852481] <TASK> [ 4316.857214] mlx5erepneighentryrelease+0x93/0x790 [mlx5core] [ 4316.858258] mlx5erepencapentrydetach+0xa7/0xf0 [mlx5core] [ 4316.859134] mlx5eencapdealloc+0xa3/0xf0 [mlx5core] [ 4316.859867] cleanencapdests.part.0+0x5c/0xe0 [mlx5core] [ 4316.860605] mlx5etcdelfdbflow+0x32a/0x810 [mlx5core] [ 4316.862609] __mlx5etcdelfdbpeerflow+0x1a2/0x250 [mlx5core] [ 4316.863394] mlx5etcdelflow+0x(/0x630 [mlx5core] [ 4316.864090] mlx5eflowput+0x5f/0x100 [mlx5core] [ 4316.864771] mlx5edeleteflower+0x4de/0xa40 [mlx5core] [ 4316.865486] tcsetupcbreoffload+0x20/0x80 [ 4316.865905] flreoffload+0x47c/0x510 [clsflower] [ 4316.869181] tcfblockplaybackoffloads+0x91/0x1d0 [ 4316.869649] tcfblockunbind+0xe7/0x1b0 [ 4316.870049] tcfblockoffloadcmd.isra.0+0x1ee/0x270 [ 4316.879266] tcfblockoffloadunbind+0x61/0xa0 [ 4316.879711] __tcfblockput+0xa4/0x310