LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux networking flaw can mishandle aggregated packets during IPv4/IPv6 translation and forwarding. The reported consequence is protocol inconsistency and reduced throughput, particularly in hotspot-like environments with IPv6-only upstream connectivity. The supplied sources do not establish code execution, data theft, or system compromise.

Executive priority

Treat this as a targeted network-reliability issue pending vendor severity information. Prioritize validation and patching for internet gateways, hotspots, and translation infrastructure where degraded throughput affects service availability. Broader emergency response is not supported by the supplied evidence.

Technical view

XLAT changes only the head packet header in certain GRO frag_list packets. Without SKB_GSO_DODGY, GSO may select skb_segment_list and process untranslated fragments inconsistently. The kernel fix marks translated GSO packets as dodgy, forcing the safer skb_segment path.

Likely exposure

Exposure is most plausible on affected Linux systems forwarding GRO/GSO traffic through BPF IPv4-to-IPv6 or IPv6-to-IPv4 translation. Ordinary hosts not performing this forwarding and XLAT workflow may be less exposed. The supplied version data is ambiguous and should be verified against vendor advisories.

Exploitation context

The bundle reports a throughput and packet-processing problem, not active exploitation. CVE-2026-23154 is not identified as KEV in the supplied data. No exploit method, observed attacks, or CVSS score is provided; absence from KEV does not prove exploitation is impossible.

Researcher notes

The affected-version representation contains duplicate commit identifiers and unclear version boundaries, so precise range conclusions are unsafe. Review the CVE record and stable commits for branch-specific applicability. Available evidence describes an unsafe segmentation-path selection after XLAT header modification, with performance and protocol-consistency effects.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant stable fix.
  • Check Linux distribution or appliance vendor guidance for exact affected and fixed releases.
  • Prioritize affected gateways, hotspots, translators, and other systems forwarding XLAT traffic.
  • Use supported network configurations to avoid the affected translation path until updated, if operationally feasible.

Validation and detection

  • Inventory Linux systems performing forwarding with BPF IPv4/IPv6 protocol translation.
  • Record kernel, distribution, and appliance firmware versions on potentially exposed systems.
  • Confirm with the vendor whether each installed build contains the cited stable fix.
  • After updating, test translated forwarding throughput and packet consistency under representative traffic.
  • Monitor affected paths for unexplained throughput degradation or protocol errors.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23154 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9fd1ff5d2ac7181844735806b0a703c942365291, 9fd1ff5d2ac7181844735806b0a703c942365291, 9fd1ff5d2ac7181844735806b0a703c942365291, 9fd1ff5d2ac7181844735806b0a703c942365291, 9fd1ff5d2ac7181844735806b0a703c942365291unaffected
LinuxLinux5.6, 0, 6.1.167, 6.6.130, 6.12.69, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.