In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix slab-out-of-bounds when handling team device events The mlx5_handle_changeupper_event() and mlx5_handle_changeinfodata_event() functions check for LAG masters (which includes both bonding and team devices) but only call bonding-specific APIs. When processing team device events, calling bond_slave_get_rcu() and bond_is_slave_inactive() on team_port structures causes KASAN to detect an out-of-bounds memory access since team_port is smaller than bond slave. Fix this by wrapping the bond-specific API calls with a check for bonding devices. This allows the function to still process LAG events for both bonding and teams but only calls bond-specific functions when dealing with actual bonding devices. For mlx5_handle_changeinfodata_event(), keep the explicit bond check as mlx5 doesn't handle state information for team ports anyway. Tested with Mellanox ConnectX-5 on Linux 7.2.0-rc6: - Bonding: PASS (no regressions) - Team device: PASS (no KASAN errors)
https://git.kernel.org/stable/c/8117cbc504cb01980258d8a8c9be8f57cf0aaceb
https://git.kernel.org/stable/c/3a6e67ff267af2053a793825c3b7844741fed461
https://git.kernel.org/stable/c/16ca0e79f31ea810346a79dda545ba344ede1d47
https://git.kernel.org/stable/c/04c824940d52871c49866a4ac67b504146f7cf35