Skip to main content
VulnerabilityPublished Updated

CVE-2026-100236: Out-of-bounds Write

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-100236· High 8.6

Not known to be exploited · CVSS 8.6 High : patch Red Hat Enterprise Linux 10 soon.

Data as of 3 Nov 2026, 19:58 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.18.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 10dpdkAffected–Fixed in–
Red Hat Enterprise Linux 9dpdkAffected–Fixed in–
Fast Datapath for RHEL 10groutAffected–Fixed in–
Fast Datapath for RHEL 10openvswitch3.5Affected–Fixed in–
Fast Datapath for RHEL 10openvswitch3.6Affected–Fixed in–
Fast Datapath for RHEL 8openvswitch2.11Affected–Fixed in–

AI-suggested

A security update for DPDK is available from Red Hat for Red Hat Enterprise Linux 10 that addresses this vulnerability along with several others. Users should apply the official vendor patch as detailed in Red Hat Advisory RHSA-2026:94630. Since a fix is available, remediation should be performed promptly by updating to the patched DPDK package versions. No additional mitigations are specified by the vendor advisory.

Description

A vulnerability in the DPDK GSO library allows a remote or guest-supplied packet to trigger an out-of-bounds read or write due to improper validation of packet header size during software GSO processing. This flaw can cause memory corruption by underflowing the payload-size calculation when a header longer than the configured GSO segment size is copied without adequate bounds checking.

References

Community reviews

Loading reviews…