Answer in brief
CVE-2026-45860 records a High severity (CVSS 7.5) vulnerability in netfilter: nf_conncount: increase the connection clean up limit to 64. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-45860 records a High severity (CVSS 7.5) vulnerability in netfilter: nf_conncount: increase the connection clean up limit to 64. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f106694733c66a48740c25bc4e212e9b2ea364ce <a5c9e14e0e8923218ae881d5e78c990c07694966 || >=be69850b461e7b491d87a22e33ab76fdd04b725e <13eede458fdf231f1bf96a398feea4ad1553f14c || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <fa85432d58c8e74b39333edbf8d28df2985dfc79 || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <0792ad077d776c2dcf20f0484e2461ded1b77a24 || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <3d0994ed0aa1fc0a2c5e620b765e8defdd021bff || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <6e5fa7add3e76da068a478d905be64be8fa4e80a || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <0af0812baf2d363176c9b76fc07e33f13aede8db || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <21d033e472735ecec677f1ae46d6740b5e47a4f3 || >=5.10.248 <5.10.252 || >=5.15.198 <5.15.202 | a5c9e14e0e8923218ae881d5e78c990c07694966, 13eede458fdf231f1bf96a398feea4ad1553f14c, fa85432d58c8e74b39333edbf8d28df2985dfc79, 0792ad077d776c2dcf20f0484e2461ded1b77a24, 3d0994ed0aa1fc0a2c5e620b765e8defdd021bff, 6e5fa7add3e76da068a478d905be64be8fa4e80a, 0af0812baf2d363176c9b76fc07e33f13aede8db, 21d033e472735ecec677f1ae46d6740b5e47a4f3, 5.10.252, 5.15.202 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f106694733c66a48740c25bc4e212e9b2ea364ce <a5c9e14e0e8923218ae881d5e78c990c07694966 || >=be69850b461e7b491d87a22e33ab76fdd04b725e <13eede458fdf231f1bf96a398feea4ad1553f14c || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <fa85432d58c8e74b39333edbf8d28df2985dfc79 || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <0792ad077d776c2dcf20f0484e2461ded1b77a24 || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <3d0994ed0aa1fc0a2c5e620b765e8defdd021bff || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <6e5fa7add3e76da068a478d905be64be8fa4e80a || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <0af0812baf2d363176c9b76fc07e33f13aede8db || >=d265929930e2ffafc744c0ae05fb70acd53be1ee <21d033e472735ecec677f1ae46d6740b5e47a4f3 || >=5.10.248 <5.10.252 || >=5.15.198 <5.15.202 | a5c9e14e0e8923218ae881d5e78c990c07694966, 13eede458fdf231f1bf96a398feea4ad1553f14c, fa85432d58c8e74b39333edbf8d28df2985dfc79, 0792ad077d776c2dcf20f0484e2461ded1b77a24, 3d0994ed0aa1fc0a2c5e620b765e8defdd021bff, 6e5fa7add3e76da068a478d905be64be8fa4e80a, 0af0812baf2d363176c9b76fc07e33f13aede8db, 21d033e472735ecec677f1ae46d6740b5e47a4f3, 5.10.252, 5.15.202 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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
Quoted source text, attributed separately from HOL analysis.