Back to CVE records
High 7.8Published Dec 23, 2025

CVE-2025-68340team: Move team device type change at the end of team_port_add

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

In the Linux kernel, the following vulnerability has been resolved: team: Move team device type change at the end of team_port_add Attempting to add a port device that is already up will expectedly fail, but not before modifying the team device header_ops. In the case of the syzbot reproducer the gre0 device is already in state UP when it attempts to add it as a port device of team0, this fails but before that header_ops->create of team0 is changed from eth_header to ipgre_header in the call to team_dev_type_check_change. Later when we end up in ipgre_header() struct ip_tunnel* points to nonsense as the private data of the device still holds a struct team. Example sequence of iproute2 commands to reproduce the hang/BUG(): ip link add dev team0 type team ip link add dev gre0 type gre ip link set dev gre0 up ip link set dev gre0 master team0 ip link set dev team0 up ping -I team0 1.1.1.1 Move team_dev_type_check_change down where all other checks have passed as it changes the dev type with no way to restore it in case one of the checks that follow it fail. Also make sure to preserve the origial mtu assignment: - If port_dev is not the same type as dev, dev takes mtu from port_dev - If port_dev is the same type as dev, port_dev takes mtu from dev This is done by adding a conditional before the call to dev_set_mtu to prevent it from assigning port_dev->mtu = dev->mtu and instead letting team_dev_type_check_change assign dev->mtu = port_dev->mtu. The conditional is needed because the patch moves the call to team_dev_type_check_change past dev_set_mtu. Testing: - team device driver in-tree selftests - Add/remove various devices as slaves of team device - syzbot

CVSS
7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Modified
Record last updated
Oct 16, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from 1d76efe1577b4323609b1bcbfafa8b731eda071a before f82d1fb65549de241fe312fcb2bcb8e0ad7b424d; from 1d76efe1577b4323609b1bcbfafa8b731eda071a before c8b15b0d2eec3b5c7f585e5a53dfc8d36c818283; from 1d76efe1577b4323609b1bcbfafa8b731eda071a before a74ab1b532ecc5f9106621a8f75b4c3d04466b35; from 1d76efe1577b4323609b1bcbfafa8b731eda071a before e26235840fd961e4ebe5568f11a2a078cf726663; from 1d76efe1577b4323609b1bcbfafa8b731eda071a before 4040b5e8963982a00aa821300cb746efc9f2947e; from 1d76efe1577b4323609b1bcbfafa8b731eda071a before e3eed4f038214494af62c7d2d64749e5108ce6ca; 1d76efe1577b4323609b1bcbfafa8b731eda071a builds before 0ae9cfc454ea5ead5f3ddbdfe2e70270d8e2c8ef
CNA record
linux linux_kernel
linux:linux_kernel
from 3.7 before 5.15.199; from 5.16 before 6.1.162; from 6.2 before 6.6.123; from 6.7 before 6.12.61; from 6.13 before 6.17.11; 6.18; 6.18; 6.18; and 4 more ranges
NVD

References

  • patch
  • patch
  • patch
  • patch
  • patch
  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.