Linux KernelOperating system · Linux
CVE-2026-43114
A fix is available.
Upgrade to 6.6.136 / 6.12.83 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable
No privileges
Zero-click
Patch available
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry New test case fails unexpectedly when avx2 matching functions are used. The test first loads a ranomly generated pipapo set with 'ipv4 . port' key, i.e. nft -f foo. This works. Then, it reloads the set after a flush: (echo flush set t s; cat foo) | nft -f - This is expected to work, because its the same set after all and it was already loaded once. But with avx2, this fails: nft reports a clashing element. The reported clash is of following form: We successfully re-inserted a . b c . d Then we try to insert a . d avx2 finds the already existing a . d, which (due to 'flush set') is marked as invalid in the new generation. It skips the element and moves to next. Due to incorrect masking, the skip-step finds the next matching element *only considering the first field*, i.e. we return the already reinserted "a . b", even though the last field is different and the entry should not have been matched. No such error is reported for the generic c implementation (no avx2) or when the last field has to use the 'nft_pipapo_avx2_lookup_slow' fallback. Bisection points to 7711f4bb4b36 ("netfilter: nft_set_pipapo: fix range overlap detection") but that fix merely uncovers this bug. Before this commit, the wrong element is returned, but erronously reported as a full, identical duplicate. The root-cause is too early return in the avx2 match functions. When we process the last field, we should continue to process data until the entire input size has been consumed to make sure no stale bits remain in the map.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
Affected:
>= 5.7, < 6.6.136>= 6.7, < 6.12.83>= 6.13, < 6.18.24>= 6.19, < 6.19.14= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped
Upgrade available
Upgrade to 6.6.136 / 6.12.83 / 6.18.24 or later
Fixed in
6.6.1366.12.836.18.24
Vendor patch
git.kernel.org →
Recommended fix
High confidence
Upgrade to kernel version 6.6.136 or later (for 6.6.x branch), 6.12.83 or later (for 6.7-6.12.x branch), 6.18.24 or later (for 6.13-6.18.x branch), or 6.19.14 or later (for 6.19.x branch)
- Identify the currently running Linux kernel version using 'uname -r'
- Determine which version branch your kernel is based on (e.g., 6.6.x, 6.7.x, 6.13.x, 6.19.x)
- Upgrade the kernel to a version that includes the fix: for 6.6.x branch upgrade to >= 6.6.136, for 6.7-6.12.x upgrade to >= 6.12.83, for 6.13-6.18.x upgrade to >= 6.18.24, for 6.19.x upgrade to >= 6.19.14
- Use your distribution's package manager to install the updated kernel (e.g., 'apt update && apt install linux-image-<version>' for Debian/Ubuntu, 'yum update kernel' for RHEL/CentOS, or 'dnf upgrade kernel' for Fedora)
- Reboot the system to load the new kernel
- Verify the fix is applied by checking the kernel version matches or exceeds the fixed release
Caveat Kernel upgrades may require reboot and could have compatibility implications with custom kernel modules or specific hardware drivers; ensure backups and test in non-production environment first
Generated from the published advisory — verify against the referenced sources before acting.
We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300.
Get the upgrade done
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-43114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43114 in production — separate from our analysis above.
Know something about CVE-2026-43114?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data