A flaw was found in the linux kernels implementation of DCCP protocol in which a local user can create a memory leak by setting options on a dccp socket. An attacker must have a local account access on the system, this is not a remote attack.
Created kernel tracking bugs for this issue:
Affects: fedora-all [bug 1791960]
That was fixed for Fedora with the 5.1 kernel rebases.
As the DCCP module will be auto-loaded when required, its use can be disabled. Red Hat Enterprise Linux 7.5 (and later) and 8.0 (and later) already have this disabled, but for any other version, the system can prevent the module from loading with the following instructions :
# echo "install dccp /bin/true" >> /etc/modprobe.d/disable-dccp.conf
The system will need to be restarted if the DCCP modules are loaded. In most circumstances, the DCCP kernel modules will be unable to be unloaded while any network interfaces are active and the protocol is in use.
If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services.