Red Hat Product Security is aware of this issue. Updates will be released as they become available. For additional information, please refer to the Red Hat Knowledgebase article: https://access.redhat.com/articles/3553061
This issue affects the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 6, 7, its real-time kernel, Red Hat Enterprise MRG 2, Red Hat Enterprise Linux 7 for ARM 64, and Red Hat Enterprise Linux 7 for Power 9. Future kernel updates for the respective releases will address this issue.
This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, but to a lesser degree. As such, the issue severity for RHEL5 is considered Moderate. This is not currently planned to be addressed in future updates of the product due to its life cycle and the issue severity. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
CVSS v3 metrics
|CVSS3 Base Score||7.5|
|CVSS3 Base Metrics||CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H|
Red Hat Security Errata
|Red Hat Enterprise Linux Advanced Update Support 6.5 (kernel)||RHSA-2018:2933||2018-10-16|
|Red Hat Enterprise Linux Advanced Update Support 6.6 (kernel)||RHSA-2018:2924||2018-10-16|
|Red Hat Enterprise Linux Extended Update Support 7.3 (kernel)||RHSA-2018:2785||2018-09-25|
|Red Hat Enterprise Linux Advanced Update Support 6.4 (kernel)||RHSA-2018:2791||2018-09-25|
|Red Hat Enterprise Linux 6 (kernel)||RHSA-2018:2846||2018-10-09|
|Red Hat Enterprise Linux Extended Update Support 6.7 (kernel)||RHSA-2018:2925||2018-10-17|
|Red Hat Enterprise Linux Server TUS (v. 6.6) (kernel)||RHSA-2018:2924||2018-10-16|
Affected Packages State
|Red Hat Enterprise MRG 2||kernel-rt||Affected|
|Red Hat Enterprise Linux 7||kernel-rt||Affected|
|Red Hat Enterprise Linux 7||kernel-alt||Affected|
|Red Hat Enterprise Linux 5||kernel||Will not fix|
AcknowledgementsRed Hat would like to thank Juha-Matti Tilli (Aalto University - Department of Communications and Networking and Nokia Bell Labs) for reporting this issue.
One may change the default 4MB and 3MB values of net.ipv4.ipfrag_high_thresh and net.ipv4.ipfrag_low_thresh (and their ipv6 counterparts net.ipv6.ipfrag_high_thresh and net.ipv6.ipfrag_low_thresh) to 256 kB and 192 kB (respectively) or below. Tests show some to significant CPU saturation drop during an attack, depending on a hardware, configuration and environment.
There can be some impact on performance though, due to ipfrag_high_thresh of 262144 bytes, as only two 64K fragments can fit in the reassembly queue at the same time. For example, there is a risk of breaking applications that rely on large UDP packets.
See the Mitigation section in the https://access.redhat.com/articles/3553061 article for the script to quickly change to/from default and lower settings.