Bug 2541488 (CVE-2026-100236) - CVE-2026-100236 dpdk: dpdk: heap out-of-bounds read/write in GSO header copy
Summary: CVE-2026-100236 dpdk: dpdk: heap out-of-bounds read/write in GSO header copy
Keywords:
Status: NEW
Alias: CVE-2026-100236
Deadline: 2026-12-25
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2552375 2552376
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 15:57 UTC by OSIDB Bzimport
Modified: 2026-10-14 15:14 UTC (History)
30 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 15:57:36 UTC
A flaw was found in DPDK lib/gso. hdr_segment_init() copies pkt_hdr_offset bytes from the first mbuf segment into a newly allocated header mbuf using rte_memcpy without checking that the source first segment is long enough or that the destination mbuf has enough tailroom. pkt_hdr_offset is taken from mbuf l2/l3/l4 (and outer) length fields, which applications commonly populate from packet headers including IP IHL and TCP data offset. A related uint16_t subtraction (gso_size - hdr_offset) underflows when the header is larger than gso_size. An application that runs software GSO on packets from an untrusted source (for example a guest via vhost, or scatter RX) can therefore read or write past mbuf bounds.


Note You need to log in before you can comment on or make changes to this bug.