Bug 2538850 (CVE-2026-57222) - CVE-2026-57222 suricata: Suricata: Incorrect detection state due to IPPair hash collision
Summary: CVE-2026-57222 suricata: Suricata: Incorrect detection state due to IPPair ha...
Keywords:
Status: NEW
Alias: CVE-2026-57222
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2539175
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-22 20:54 UTC by OSIDB Bzimport
Modified: 2026-09-23 08:32 UTC (History)
0 users

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-22 20:54:37 UTC
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to 7.0.17 and 8.0.6, crafted IPv4 and IPv6 address pairs can collide in the IPPair hash because src/ippair.c did not compare the IP address family before reusing IPPair-backed state. This can apply state from one IP family to another for xbits track ip_pair, FTP data expectations, and, on the 7.0 release line, thresholding, detection_filter, and rate_filter rules using track by_both, causing incorrect detection state. This issue is fixed in versions 8.0.6 and 7.0.17.


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