High 8.6Published Jun 3, 2026

CVE-2026-46273ibmveth: Disable GSO for packets with small MSS

Updated under an hour ago (Oct 26, 2026, 9:30 PM ET)

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.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: ibmveth: Disable GSO for packets with small MSS Some physical adapters on Power systems do not support segmentation offload when the MSS is less than 224 bytes. Attempting to send such packets causes the adapter to freeze, stopping all traffic until manually reset. Implement ndo_features_check to disable GSO for packets with small MSS values. The network stack will perform software segmentation instead. The 224-byte minimum matches ibmvnic commit <f10b09ef687f> ("ibmvnic: Enforce stronger sanity checks on GSO packets") which uses the same physical adapters in SEA configurations. The issue occurs specifically when the hardware attempts to perform segmentation (gso_segs > 1) with a small MSS. Single-segment GSO packets (gso_segs == 1) do not trigger the problematic LSO code path and are transmitted normally without segmentation. Add an ndo_features_check callback to disable GSO when MSS < 224 bytes. Also call vlan_features_check() to ensure proper handling of VLAN packets, particularly QinQ (802.1ad) configurations where the hardware parser may not support certain offload features. Validated using iptables to force small MSS values. Without the fix, the adapter freezes. With the fix, packets are segmented in software and transmission succeeds. Comprehensive regression testing completedd (MSS tests, performance, stability).

CVSS: 8.6 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Weakness (CWE): CWE-400
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: Aug 7, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	8641dd85799f85bef5f0d1f87356aaa12cb2195e builds before 86fc64584811d43c9ccd74447de58620189d8b77; 8641dd85799f85bef5f0d1f87356aaa12cb2195e builds before 9a5e984d7af910e46dcbed3ce77873e000a4f77d; 8641dd85799f85bef5f0d1f87356aaa12cb2195e builds before 1cdf5dbcec988d06f5f720bdf89e91073f77fa10; 8641dd85799f85bef5f0d1f87356aaa12cb2195e builds before 82bc89fbb82d9396fb4eaee8720ea85e2e787957; from 8641dd85799f85bef5f0d1f87356aaa12cb2195e before db8012c631cb845e9ae2b4b531e17d86c9519755; from 8641dd85799f85bef5f0d1f87356aaa12cb2195e before c1f261863e65b508f37416dfbc5c5d911c9b9233; 8641dd85799f85bef5f0d1f87356aaa12cb2195e builds before 3af24f0c4c31f18a4a2d927990759194832bb6e9; from 8641dd85799f85bef5f0d1f87356aaa12cb2195e before cc427d24ac6442ffdeafd157a63c7c5b73ed4de4	CNA record
linux linux_kernel linux:linux_kernel	from 4.2 before 5.10.258; from 5.11 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.140; from 6.7 before 6.12.88; from 6.13 before 6.18.30; from 6.19 before 7.0.7; 7.1	NVD

References

References

https://git.kernel.org/stable/c/86fc64584811d43c9ccd74447de58620189d8b77	patch
https://git.kernel.org/stable/c/9a5e984d7af910e46dcbed3ce77873e000a4f77d	patch
https://git.kernel.org/stable/c/1cdf5dbcec988d06f5f720bdf89e91073f77fa10	patch
https://git.kernel.org/stable/c/82bc89fbb82d9396fb4eaee8720ea85e2e787957	patch
https://git.kernel.org/stable/c/db8012c631cb845e9ae2b4b531e17d86c9519755	patch
https://git.kernel.org/stable/c/c1f261863e65b508f37416dfbc5c5d911c9b9233	patch
https://git.kernel.org/stable/c/3af24f0c4c31f18a4a2d927990759194832bb6e9	patch
https://git.kernel.org/stable/c/cc427d24ac6442ffdeafd157a63c7c5b73ed4de4	patch

The CVE record on cve.org NVD's entry

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.