VulnerabilityPublished 18 Oct 2026

CVE-2026-98557: Linux kernel · gve: DQO: fix header length used by gve_can_send_tso() for UDP GSO

Source GCVE Database

Authoritative record:CVE-2026-98557· Medium

Not known to be exploited · fixed in feab3880a72b43913d332c06b75bb80526fa47ba : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in feab3880a72b43913d332c06b75bb80526fa47ba, dc9e8964a21f20620dbfca4ef3e11eefa7be6451, 83769c23fb1879edc916a526ba424285033baf2d

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-jvwf-rjpr-3g5x

What to do

Upgrade Linux kernel to feab3880a72b43913d332c06b75bb80526fa47ba, dc9e8964a21f20620dbfca4ef3e11eefa7be6451 or 83769c23fb1879edc916a526ba424285033baf2d.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 2f855c52a2e1d3c40d186549ac46cbd88b38eb49, < feab3880a72b43913d332c06b75bb80526fa47ba	Fixed in feab3880a72b43913d332c06b75bb80526fa47ba
LinuxLinux	Affected ≥ 014c607f86abc903d7bf46e13373d89392e371fe, < dc9e8964a21f20620dbfca4ef3e11eefa7be6451	Fixed in dc9e8964a21f20620dbfca4ef3e11eefa7be6451
LinuxLinux	Affected ≥ 014c607f86abc903d7bf46e13373d89392e371fe, < 83769c23fb1879edc916a526ba424285033baf2d	Fixed in 83769c23fb1879edc916a526ba424285033baf2d
LinuxLinux	Affected =7.1	Fixed in–

AI-suggested

A fix has been applied in the Linux kernel to correctly handle header length calculation for UDP GSO packets in the gve driver. Users should update to the patched kernel version containing this fix. Since this is a kernel-level fix, upgrading the kernel is the recommended remediation. No alternative mitigations are indicated.

Description

A vulnerability in the Linux kernel's gve driver related to UDP Generic Segmentation Offload (GSO) was resolved. The function gve_can_send_tso() incorrectly calculates header length for UDP GSO packets by using a TCP header length function, leading to miscalculated segment boundaries. This can cause either unnecessary disabling of GSO or handing the device packets with segments spanning too many buffers. The fix involves using the correct UDP header length for these packets.

Impact

Miscalculation of header length in UDP GSO packets can lead to two main impacts: (1) unnecessary disabling of GSO, causing the network stack to segment packets inefficiently, potentially degrading performance; (2) the driver may provide the device with packets whose segments span more buffers than supported, which could lead to transmission errors or dropped packets. There is no indication of code execution or data corruption from this issue.

References

Community reviews

Loading reviews…