Bug 2565198 - CVE-2026-119299 inspektor-gadget: gopacket: Denial of Service via crafted SCTP packets [fedora-43]
Summary: CVE-2026-119299 inspektor-gadget: gopacket: Denial of Service via crafted SCT...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: inspektor-gadget
Version: 43
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Kyle Gospodnetich
QA Contact:
URL:
Whiteboard: {"flaws": ["f9928d07-9c31-47b7-acf6-a...
Depends On:
Blocks: CVE-2026-119299
TreeView+ depends on / blocked
 
Reported: 2026-11-02 14:25 UTC by Yadnyawalk Tale
Modified: 2026-11-02 14:25 UTC (History)
3 users (show)

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


Attachments (Terms of Use)

Description Yadnyawalk Tale 2026-11-02 14:25:50 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

gopacket provides packet processing capabilities for Go. Prior to 1.7.2, the SCTP chunk chain in layers/sctp.go passes attacker-controlled declared lengths and counts to decodeSCTPInit, decodeSCTPShutdown, decodeSCTPError, decodeSCTPSack, and decodeSCTPParameter without checking that each chunk contains the fixed fields, parameter TLVs, gap acknowledgements, or duplicate TSNs those sub-decoders read. A crafted SCTP segment can therefore cause out-of-bounds or inverted slice panics; the panic can terminate applications that use gopacket.DecodeOptions.SkipDecodeRecovery, direct registered decoders, or DecodingLayerParser with IgnorePanic enabled, while the default recovery-enabled APIs convert it to a per-packet decode error. This is the SCTP sub-decoder residual named but not remediated by CVE-2026-65819, whose version 1.7.1 changes bounded the generic dispatcher but left these per-type reads and loops unchecked. The impact is availability only, with no data disclosure, modification, or allocation amplification. This issue is fixed in version 1.7.2.


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