Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1422081 - (CVE-2017-5972) CVE-2017-5972 kernel: SYN cookie protection mechanism not properly implemented
CVE-2017-5972 kernel: SYN cookie protection mechanism not properly implemented
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170212,repor...
: Security
Depends On:
Blocks: 1422084
  Show dependency treegraph
 
Reported: 2017-02-14 07:41 EST by Andrej Nemec
Modified: 2018-02-04 19:07 EST (History)
42 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-04 19:07:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-02-14 07:41:47 EST
The TCP stack in the Linux kernel 3.x does not properly implement a SYN cookie protection mechanism for the case of a fast network connection, which allows remote attackers to cause a denial of service (CPU consumption) by sending many TCP SYN packets.

The belief is that the system spends considerable time generating TCP syn cookies and creates a soft lockup in the system, reducing its ability to handle other requests.  This is as the syn cookie generation is serialized per system and not per CPU.  Other CPU's on the system can continue to work correctly.

References:

https://cxsecurity.com/issue/WLB-2017020112
https://githubengineering.com/syn-flood-mitigation-with-synsanity/
Comment 2 Wade Mealing 2017-03-02 23:34:25 EST
Statement:

This issue affects Red Hat Enterprise Linux 5,6, 7 and MRG-2 kernels.  Red Hat has no plans to fix this issue at this time.

While performance enhancements have been made upstream, Red Hat Product Security believes the report to be invalid and able to be mitigated with synproxy.  This flaw is currently under investigation for validity and Red Hat is asking to revoke the CVE.

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