gve: DQO: reject TSO packets with an out of range MSS

Summary

In the Linux kernel, the following vulnerability has been resolved: gve: DQO: reject TSO packets with an out of range MSS gve_prep_tso() notes that the device requires the MSS to be <= 9728, but does not enforce it, assuming the 9K MTU enforced by the hypervisor and the 64KB limit on TSO sizes are enough. This does not hold for packets that were not generated locally. A guest behind a tap, or any packet socket user, can provide an arbitrary gso_size in virtio_net_hdr. Layer 2 forwarding does not check the MTU for GSO packets (is_skb_forwardable()), and gso_features_check() only bounds skb->len and gso_segs, never gso_size. Such a packet reaches gve_tx_fill_tso_ctx_desc(), which puts gso_size into the mss field of the TSO context descriptor. This field is 14 bits wide, so a gso_size of 16384 is silently turned into an MSS of zero. Drop these packets from gve_prep_tso(), and make sure that gve_features_check_dqo() leaves their GSO bits alone: skb_segment() splits at gso_size regardless of the MTU, so falling back to software segmentation would give the device non TSO packets bigger than the 9728 bytes it supports. Note that the device can still be given oversized non TSO packets when the stack segments in software for other reasons, for instance after TSO has been disabled with ethtool. This is a generic issue, because the MTU check is skipped for GSO packets in the forwarding path, and is addressed separately.

Timeline

1. Oct 18, 2026, 3:18 PM UTCCVE published
2. Oct 19, 2026, 9:21 AM UTCRecord last updated

Affected versions

• Linux Linux

  From a57e5de476be0b4b7f42beb6a21c19ad9c577aa3 · fixed in 2dc3ae3942e151fef254b7bbb65c832192ad2069; From a57e5de476be0b4b7f42beb6a21c19ad9c577aa3 · fixed in c517e8755960c8c6335ebf7dae6c95c43e5fb085; From a57e5de476be0b4b7f42beb6a21c19ad9c577aa3 · fixed in 296c83b5ccc808c080865eb20fd7a477b0355bb7

• Linux Linux

  5.14

• KernelLinux

  From 5.14.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9

References 3