Vulnerability · Published Jul 20, 2026 · Assigned by Linux

CVE-2026-64190net: team: fix NULL pointer dereference in team_xmit during mode change

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-64190
Debian:13linux6.12.115-2DEBIAN-CVE-2026-64190
Debian:14linux7.1.3-1DEBIAN-CVE-2026-64190
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-64190
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-64190
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-64190
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-64190

Affected products (as reported)

VendorProductVersions
Linux Linux 3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before d61bf3bc17de1e18cbdac94cf5389bb9dc2ddfe73d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before ac342f86638f5e184c8511cff12a421aea56acc63d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before a879f78c478cee77f4bd43e92225a640c23f45d43d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before 9486377e5e971988a3add171c398eb654a866fab3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before cde5c7f0286c4203d0abc7248201542aa8bf33bb3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before 03e9405c518c4d61f28079492f252d6d4e2bac5c3d249d4ca7d0ed6629a135ea1ea21c72286c0d80 – before 25fe708bbc59289d3d1ea4b126fbc1b460a072a5
Linux Linux 3.3

References