netfilter: nf_conncount: increase the connection clean up limit to 64
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d265929930e2ffafc744c0ae05fb70acd53be1ee · < 6e5fa7add3e76da068a478d905be64be8fa4e80a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_conncount: increase the connection clean up limit to 64
After the optimization to only perform one GC per jiffy, a new problem was introduced. If more than 8 new connections are tracked per jiffy the list won't be cleaned up fast enough possibly reaching the limit wrongly.
In order to prevent this issue, only skip the GC if it was already triggered during the same jiffy and the increment is lower than the clean up limit. In addition, increase the clean up limit to 64 connections to avoid triggering GC too often and do more effective GCs.
This has been tested using a HTTP server and several performance tools while having nft_connlimit/xt_connlimit or OVS limit configured.
Output of slowhttptest + OVS limit at 52000 connections:
slow HTTP test status on 340th second: initializing: 0 pending: 432 connected: 51998 error: 0 closed: 0 service available: YES
From the CVE record · Linux
The Linux kernel’s netfilter nf_conncount cleanup can fall behind when more than eight new connections are tracked per jiffy, causing a connection limit to be reached incorrectly. A remote source of connections may trigger this condition; the input does not establish authentication requirements or user interaction.
Operators running Linux kernels with nft_connlimit, xt_connlimit, or an OVS connection limit configured should check their kernel version; affected versions were not provided.