CVE-2026-80668: Linux
- Severity
- 9.8 (CRITICAL)
- Vendor
- LINUX
- Affected versions
- bffcaad9afdfe45d7fc777397d3b83c1e3ebffe5 through before 7ec786f4230c2a9b2eaf97a2d45368933b49d2b2; bffcaad9afdfe45d7fc777
- Patch status
- Patched
- Published
- 2026-08-28T08:16:52.080
- Modified
- 2026-08-29T07:16:49.200
Why it matters
Critical vulnerability requiring immediate validation against your environment.
Recommended admin actions
- Prioritize validation immediately due to critical CVSS severity.
- Compare installed versions against the affected version range in the advisory.
Technical summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_expect: use conntrack GC to reap expectations This patch replaces the timer API by GC worker approach for expectations, as it already happened in many other subsystems. Use the existing conntrack GC worker to iterate over the local list of expectations in the master conntrack to reap expired expectations. Check IPS_HELPER_BIT to run GC for expectations, set it on for nft_ct expectation which nevers sets it. Hold the expectation spinlock while iterating over the master conntrack expectation list to synchronize with nf_ct_remove_expectations(). This also performs runtime packet path garbage collection through the expectation insertion and lookup functions while walking over one of the chains of the global expectation hashtables. Unconfirmed conntrack entries are skipped since ct->ext can be reallocated and dying are skipped since those will be gone soon. Set on IPS_HELPER_BIT if the helper ct extension is added, then the new GC worker does not need to bump the ct refcount to check if the ct->ext helper is available. This removes the extra bump on the refcount for expectation timers, this allows to remove several nf_ct_expect_put() calls after the unlink, after this update only refcount remains at 1 while on the expectation hashes. This patch implicitly addresses a race with the existing timer API allowing an expectation to access a stale exp->master pointer which has been already released when expectation removal loses races with an expiring timer, ie. timer_del() reporting false. Add a new NF_CT_EXPECT_DEAD flag to reap this expectation via GC. This is needed by nf_conntrack_unexpect_related() which is called in error paths to invalidate newly created expectations that has been added into the hashes. These expectactions cannot be inmediately released as GC or nf_ct_remove_expectations() could race to make it. On expectation insert, the runtime GC reaps stale expectations before checking the expectation limit set by policy. Set current timestamp in nf_ct_expect_alloc(), then add the expectation policy timeout (or custom timeout specified added on top of this) to specify the expectation lifetime.
View the official NVD record for CVE-2026-80668
CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.
VULNERABILITY PULSE
| AFFECTED PRODUCT | ACTION | ||
|---|---|---|---|
| CVE-2026-82222 |
GiveWP PATCH
Reporter: AUDIT
|
10
CRITICAL
|
VIEW RECORD |
| CVE-2026-54745 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
10
CRITICAL
|
VIEW RECORD |
| CVE-2026-55565 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.9
CRITICAL
|
VIEW RECORD |
| CVE-2026-55634 |
pimcore PATCH
Reporter: SECURITY-ADVISORIES
|
9.9
CRITICAL
|
VIEW RECORD |
| CVE-2026-18527 |
Product identification pending
Reporter: PSIRT
|
9.9
CRITICAL
|
VIEW RECORD |
| CVE-2026-19295 |
Product identification pending
Reporter: PSIRT
|
9.9
CRITICAL
|
VIEW RECORD |
| CVE-2026-76581 |
WPMU DEV Dashboard
Reporter: SECURITY
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80600 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80609 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80612 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80617 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80630 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80634 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80668 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80673 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80674 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80681 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80694 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-80714 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-37751 |
Product identification pending
Reporter: CVE
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-55559 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-82329 |
artifactory
Reporter: REEFS
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-19286 |
Product identification pending
Reporter: PSIRT
|
9.8
CRITICAL
|
VIEW RECORD |
| CVE-2026-54754 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.6
CRITICAL
|
VIEW RECORD |
| CVE-2026-54755 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.6
CRITICAL
|
VIEW RECORD |
| CVE-2026-82244 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
9.4
CRITICAL
|
VIEW RECORD |
| CVE-2026-82078 |
PaperCut MF/NG
Reporter: EB41DAC7-0AF8-4F84-9F6D-0272772514F4
|
9.4
CRITICAL
|
VIEW RECORD |
| CVE-2026-78032 |
SOY CMS
Reporter: VULTURES
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-80671 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-80684 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-80693 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-55068 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-55220 |
pimcore PATCH
Reporter: SECURITY-ADVISORIES
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-55378 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-82266 |
redpanda
Reporter: DISCLOSURE
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-82277 |
argo-rollouts
Reporter: DISCLOSURE
|
9.3
CRITICAL
|
VIEW RECORD |
| CVE-2026-80603 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-80670 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-18918 |
Product identification pending
Reporter: EMO
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-42007 |
Product identification pending PATCH
Reporter: SECURITY
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-55247 |
plone.app.event PATCH
Reporter: SECURITY-ADVISORIES
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-55248 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-55511 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-82281 |
kotaemon
Reporter: DISCLOSURE
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-3627 |
Product identification pending
Reporter: PSIRT
|
9.1
CRITICAL
|
VIEW RECORD |
| CVE-2026-40541 |
Product identification pending PATCH
Reporter: SECURITY
|
9
CRITICAL
|
VIEW RECORD |
| CVE-2026-82021 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
9
CRITICAL
|
VIEW RECORD |
| CVE-2026-80601 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80604 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80608 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80633 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80635 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80638 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80672 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80683 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80692 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80721 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80722 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-80724 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-13761 |
Product identification pending
Reporter: SECURITY
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-81578 |
PaperCut MF/NG
Reporter: EB41DAC7-0AF8-4F84-9F6D-0272772514F4
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-55485 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-55509 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-55521 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-72984 |
Product identification pending
Reporter: SECURE
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-82282 |
Product identification pending
Reporter: DISCLOSURE
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-82285 |
Product identification pending
Reporter: DISCLOSURE
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-82286 |
Product identification pending
Reporter: DISCLOSURE
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-18729 |
Product identification pending
Reporter: PSIRT
|
8.8
HIGH
|
VIEW RECORD |
| CVE-2026-78072 |
Product identification pending
Reporter: SECURITY
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82247 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82251 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82252 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82253 |
gitoxide PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82254 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82259 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82260 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82261 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-19412 |
CP-XR-DE21-S Router
Reporter: VDISCLOSE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-55245 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-75124 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-81849 |
Product identification pending PATCH
Reporter: FF89BA41-3AA1-4D27-914A-91399E9639E5
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82268 |
Product identification pending
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82270 |
Product identification pending
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82275 |
Product identification pending
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82278 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-82288 |
Product identification pending
Reporter: DISCLOSURE
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-55763 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-75118 |
TL-MR100 v3.20
Reporter: F23511DB-6C3E-4E32-A477-6AA17D310630
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-81517 |
Product identification pending
Reporter: CNA
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-81518 |
Product identification pending
Reporter: CNA
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-81520 |
BI Connector
Reporter: CNA
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-81532 |
Product identification pending
Reporter: CNA
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-55764 |
Product identification pending PATCH
Reporter: SECURITY-ADVISORIES
|
8.7
HIGH
|
VIEW RECORD |
| CVE-2026-80590 |
Linux PATCH
Reporter: 416BAAA9-DC9F-4396-8D5F-8C081FB06D67
|
8.6
HIGH
|
VIEW RECORD |
| CVE-2026-82239 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.6
HIGH
|
VIEW RECORD |
| CVE-2026-82240 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.6
HIGH
|
VIEW RECORD |
| CVE-2026-56100 |
Product identification pending
Reporter: DISCLOSURE
|
8.6
HIGH
|
VIEW RECORD |
| CVE-2026-75121 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.6
HIGH
|
VIEW RECORD |
| CVE-2026-75122 |
Product identification pending PATCH
Reporter: DISCLOSURE
|
8.6
HIGH
|
VIEW RECORD |
About the Vulnerability Pulse CVE Feed
The Vulnerability Pulse feed tracks live CVE advisories sourced from the National Vulnerability Database and vendor security disclosures. It is designed for SOC analysts, IT administrators, and security teams who need a fast, filterable view of current vulnerabilities without digging through raw NVD data.
How to Use the CVE Advisory Tracker
Use the severity filters to narrow results to Critical or High priority vulnerabilities. Filter by vendor to focus on software and hardware relevant to your environment. Export to CSV for reporting, ticketing, or patch prioritization workflows.
What Is a CVE Advisory?
A CVE (Common Vulnerabilities and Exposures) advisory is a public disclosure of a security vulnerability assigned a unique identifier by MITRE. Advisories include severity scores (CVSS), affected versions, and remediation guidance. Monitoring CVE advisories is a core function of vulnerability management programs and SOC operations.
CVE Analysis & Writeups
For in-depth analysis of specific vulnerabilities, visit the IT Knowledge Bases blog for CVE breakdowns, exploitation analysis, and remediation guidance written for security practitioners.