Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1386646 - (CVE-2016-8106) CVE-2016-8106 kernel: DoS of Intel Ethernet controllers after a period of IPv6 fragment flood
CVE-2016-8106 kernel: DoS of Intel Ethernet controllers after a period of IPv...
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=20170109,repor...
: Security
Depends On: 1370029
Blocks: 1386648
  Show dependency treegraph
 
Reported: 2016-10-19 07:39 EDT by Adam Mariš
Modified: 2017-04-10 09:10 EDT (History)
24 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It was found that Intel® Ethernet Controller X710 family and Intel® Ethernet Controller XL710 family of products (aka Fortville) can possibly lock up and not receive any packets after a period of IPv6 fragment flood.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-04-10 08:05:30 EDT
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 Adam Mariš 2016-10-19 07:39:10 EDT
It was found that Intel® Ethernet Controller X710 family and Intel® Ethernet Controller XL710 family of products (aka Fortville) can possibly lock up and not receive any packets after a period of IPv6 fragment flood.

Product bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1370029

References:

https://nvd.nist.gov/vuln/detail/CVE-2016-8106

https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00063&languageid=en-fr
Comment 1 Vladis Dronov 2017-04-10 08:02:47 EDT
Statement:

None of the Red Hat's products are affected as the flaw was found in the Intel network card Non-Volatile Flash Memory (NVM) image (firmware).

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