CVE-2026-45860

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 7, 2026
No patch confirmed yet.
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa85432d58c8e74b39333edbf8d28df2985dfc79
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a5c9e14e0e8923218ae881d5e78c990c07694966
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e5fa7add3e76da068a478d905be64be8fa4e80a
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d0994ed0aa1fc0a2c5e620b765e8defdd021bff
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21d033e472735ecec677f1ae46d6740b5e47a4f3
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13eede458fdf231f1bf96a398feea4ad1553f14c
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0af0812baf2d363176c9b76fc07e33f13aede8db
generic

netfilter: nf_conncount: increase the connection clean up limit to 64 - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0792ad077d776c2dcf20f0484e2461ded1b77a24

Vendor Advisories for CVE-2026-45860(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 266 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 09:16 UTCEG score recompute
  3. 2026-09-14 09:16 UTCVendor advisory
  4. 2026-09-14 09:16 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 04:09 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:52 UTCEG score recompute
  24. 2026-08-25 05:52 UTCVendor advisory
  25. 2026-08-25 05:52 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 15:39 UTCEG score recompute
  2. 2026-08-23 15:39 UTCVendor advisory
  3. 2026-08-23 15:38 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 21:01 UTCEG score recompute
  7. 2026-08-21 21:01 UTCVendor advisory
  8. 2026-08-21 21:01 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 17:46 UTCEG score recompute
  11. 2026-08-20 17:46 UTCVendor advisory
  12. 2026-08-20 17:45 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:22 UTCVendor advisory
  17. 2026-08-17 09:22 UTCGHSA enrichment
  18. 2026-08-16 16:27 UTCEG score recompute
  19. 2026-08-16 16:27 UTCVendor advisory
  20. 2026-08-16 16:27 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:55 UTCEG score recompute
  23. 2026-08-16 02:55 UTCVendor advisory
  24. 2026-08-16 02:55 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 23:42 UTCVendor advisory
  28. 2026-08-14 23:42 UTCGHSA enrichment
  29. 2026-08-14 12:39 UTCVendor advisory
  30. 2026-08-14 12:39 UTCGHSA enrichment
  31. 2026-08-14 01:35 UTCEG score recompute
  32. 2026-08-14 01:35 UTCVendor advisory
  33. 2026-08-14 01:35 UTCGHSA enrichment
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-13 09:52 UTCVendor advisory
  36. 2026-08-13 09:52 UTCGHSA enrichment
  37. 2026-08-12 22:47 UTCEG score recompute
  38. 2026-08-12 22:47 UTCVendor advisory
  39. 2026-08-12 22:47 UTCGHSA enrichment
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-12 11:44 UTCVendor advisory
  42. 2026-08-12 11:44 UTCGHSA enrichment
  43. 2026-08-12 00:40 UTCEG score recompute
  44. 2026-08-12 00:40 UTCVendor advisory
  45. 2026-08-12 00:40 UTCGHSA enrichment
  46. 2026-08-11 13:37 UTCVendor advisory
  47. 2026-08-11 13:37 UTCGHSA enrichment
  48. 2026-08-11 00:15 UTCEG score recompute
  49. 2026-08-11 00:15 UTCVendor advisory
  50. 2026-08-11 00:15 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 07:13 UTCVendor advisory
  53. 2026-08-10 07:13 UTCGHSA enrichment
  54. 2026-08-09 20:09 UTCEG score recompute
  55. 2026-08-09 20:09 UTCVendor advisory
  56. 2026-08-09 20:09 UTCGHSA enrichment
  57. 2026-08-09 13:46 UTCEPSS rescore
  58. 2026-08-09 09:06 UTCVendor advisory
  59. 2026-08-09 09:06 UTCGHSA enrichment
  60. 2026-08-08 22:03 UTCEG score recompute
  61. 2026-08-08 22:03 UTCVendor advisory
  62. 2026-08-08 22:03 UTCGHSA enrichment
  63. 2026-08-08 16:37 UTCEPSS rescore
  64. 2026-08-08 10:17 UTCVendor advisory
  65. 2026-08-08 10:17 UTCGHSA enrichment
  66. 2026-08-07 23:14 UTCEG score recompute
  67. 2026-08-07 23:14 UTCVendor advisory
  68. 2026-08-07 23:14 UTCGHSA enrichment
  69. 2026-08-07 12:11 UTCVendor advisory
  70. 2026-08-07 12:11 UTCGHSA enrichment
  71. 2026-08-07 00:31 UTCEG score recompute
  72. 2026-08-07 00:31 UTCVendor advisory
  73. 2026-08-07 00:31 UTCGHSA enrichment
  74. 2026-08-06 13:47 UTCEPSS rescore
  75. 2026-08-06 11:51 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-45860?
CVE-2026-45860 is a high vulnerability published on May 27, 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…
When was CVE-2026-45860 disclosed?
CVE-2026-45860 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45860 actively exploited?
CVE-2026-45860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.6% of all scored CVEs.
What is the CVSS score of CVE-2026-45860?
CVE-2026-45860 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45860, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45860

Explore →

Is Your Infrastructure Affected by CVE-2026-45860?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.