GHSA-jmpj-vqww-cqc8 · 深刻度： medium — In the Linux kernel, the following vulnerability has been resolved: team: Move team device type...
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
総合評価: CVE-2025-68340 は低リスク（22.8/100）。CVSS 深刻度は中。悪用される可能性が高い（EPSS 0.12%、2 パーセンタイル） 推奨対応: 悪用情報と EPSS の推移を監視し、必要に応じて優先度を見直してください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.02% | 0.12% | +0.10% |
| 2 | 2026-02-27 | 0.05% | 0.02% | -0.03% |
| 3 | 2026-02-18 | — | 0.05% | — |
EPSS の全履歴 （全 4 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 5.5 | 3.1 | MEDIUM |
|
1.8 | 3.6 | [email protected] |
GHSA-jmpj-vqww-cqc8 · 深刻度： medium — In the Linux kernel, the following vulnerability has been resolved: team: Move team device type...
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
not yet assigned | CVE-2025-68340 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1. | https://security-tracker.debian.org/tracker/CVE-2025-68340 |
redhat
|
medium | — | https://access.redhat.com/security/cve/CVE-2025-68340 |
suse
|
medium | CVE-2025-68340 severity moderate: SUSE including 408 source package names (13.2-9.1:libsystemd0-254.23-1.1, 13.2-9.1:libudev1-254.23-1.1, …), 761 product×package rows across 121 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (121 product lines)): Fixed 499, Known Affected 231, First Fixed 25, Known Not Affected 6. | https://www.suse.com/security/cve/CVE-2025-68340/ |
ubuntu
|
medium | CVE-2025-68340 medium priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1405 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1010, ignored 183, released 147, needed 51, pending 13, not-affected 1. | https://ubuntu.com/security/CVE-2025-68340 |
| ベンダー | 製品 | バージョン | 生の CPE |
|---|---|---|---|
| linux | linux_kernel | >= 3.7, < 5.15.199 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.16, < 6.1.162 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.2, < 6.6.123 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.7, < 6.12.61 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.13, < 6.17.11 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc1:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc2:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc3:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:* |
| linux | linux_kernel | 6.18 | cpe:2.3:o:linux:linux_kernel:6.18:rc7:*:*:*:*:*:* |