Skip to main content
VulnerabilityPublished Updated

CVE-2026-23154: Linux kernel · net: fix segmentation of forwarding fraglist GRO

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 11:54 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in 9122d7280b2303e835cdfec156bd932ac1f586ed, 426ca15c7f6cb6562a081341ca88893a50c59fa2, 3e62db1e3140449608975e29e0979cc5f3b1cc07 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9fd1ff5d2ac7181844735806b0a703c942365291, < 9122d7280b2303e835cdfec156bd932ac1f586ed
Fixed in
  • 9122d7280b2303e835cdfec156bd932ac1f586ed
LinuxLinuxAffected
  • ≥ 9fd1ff5d2ac7181844735806b0a703c942365291, < 426ca15c7f6cb6562a081341ca88893a50c59fa2
Fixed in
  • 426ca15c7f6cb6562a081341ca88893a50c59fa2
LinuxLinuxAffected
  • ≥ 9fd1ff5d2ac7181844735806b0a703c942365291, < 3e62db1e3140449608975e29e0979cc5f3b1cc07
Fixed in
  • 3e62db1e3140449608975e29e0979cc5f3b1cc07
LinuxLinuxAffected
  • ≥ 9fd1ff5d2ac7181844735806b0a703c942365291, < 3d48d59235c494d34e32052f768393111c0806ef
Fixed in
  • 3d48d59235c494d34e32052f768393111c0806ef
LinuxLinuxAffected
  • ≥ 9fd1ff5d2ac7181844735806b0a703c942365291, < 2cbef9ea5a0ac51863ede35c45f26931a85d3888
Fixed in
  • 2cbef9ea5a0ac51863ede35c45f26931a85d3888
LinuxLinuxAffected
  • =5.6
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: net: fix segmentation of forwarding fraglist GRO This patch enhances GSO segment handling by properly checking the SKB_GSO_DODGY flag for frag_list GSO packets, addressing low throughput issues observed when a station accesses IPv4 servers via hotspots with an IPv6-only upstream interface. Specifically, it fixes a bug in GSO segmentation when forwarding GRO packets containing a frag_list. The function skb_segment_list cannot correctly process GRO skbs that have been converted by XLAT, since XLAT only translates the header of the head skb. Consequently, skbs in the frag_list may remain untranslated, resulting in protocol inconsistencies and reduced throughput. To address this, the patch explicitly sets the SKB_GSO_DODGY flag for GSO packets in XLAT's IPv4/IPv6 protocol translation helpers (bpf_skb_proto_4_to_6 and bpf_skb_proto_6_to_4). This marks GSO packets as potentially modified after protocol translation. As a result, GSO segmentation will avoid using skb_segment_list and instead falls back to skb_segment for packets with the SKB_GSO_DODGY flag. This ensures that only safe and fully translated frag_list packets are processed by skb_segment_list, resolving protocol inconsistencies and improving throughput when forwarding GRO packets converted by XLAT.

References

Community reviews

Loading reviews…