Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43114: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry

CriticalCVSS 9.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 37/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 07de44424bb7f17ef9357e8535df96d9e97c40cb, 0abbc43f71d99baadeeba6fa3fe1c80b676f57ed, 1c43f0dd8691ddf8884793b481ddc7511cf593c3.

Low priority for now. Upgrade to Linux Linux 07de44424bb7f17ef9357e8535df96d9e97c40cb, 0abbc43f71d99baadeeba6fa3fe1c80b676f57ed, 1c43f0dd8691ddf8884793b481ddc7511cf593c3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In 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.

Published
May 6, 2026
Updated
Nov 11, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
37 / 40 · 9.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.4
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43114

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before f8c39983fc9c1a978c82e6f2df7bfba8a8561587affected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before c7babe2f28b507e17f28e9f753b7caec72d4857faffected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before 1c43f0dd8691ddf8884793b481ddc7511cf593c3affected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before fa4f1f52528c73989d820f32bfca06bec5afeeceaffected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before 3d53f9aafd469ae1ea27051e00f5b96ca1b55d52affected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before 07de44424bb7f17ef9357e8535df96d9e97c40cbaffected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before 0abbc43f71d99baadeeba6fa3fe1c80b676f57edaffected · git
    • 7400b063969bdca4a06cd97f1294d765c8eecbe1 and later · before d3c0037ffe1273fa1961e779ff6906234d6cf53caffected · git
    • before 5.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.42.1.el9_85.14.0-687.42.1.el9_8

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43112May 6, 2026 · fs/smb/client: fix out-of-bounds read in cifs_sanitize_prepath
    35Monitor
  • ← EarlierCVE-2026-43113May 6, 2026 · wifi: wl1251: validate packet IDs before indexing tx_frames
    35Monitor
  • Later →CVE-2026-43115May 6, 2026 · srcu: Use irq_work to start GP in tiny SRCU
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux07de44424bb7f17ef9357e8535df96d9e97c40cbVendor (CNA)
Linux Linux0abbc43f71d99baadeeba6fa3fe1c80b676f57edVendor (CNA)
Linux Linux1c43f0dd8691ddf8884793b481ddc7511cf593c3Vendor (CNA)
Linux Linux3d53f9aafd469ae1ea27051e00f5b96ca1b55d52Vendor (CNA)
Linux Linuxc7babe2f28b507e17f28e9f753b7caec72d4857fVendor (CNA)
Linux Linuxd3c0037ffe1273fa1961e779ff6906234d6cf53cVendor (CNA)
Linux Linuxf8c39983fc9c1a978c82e6f2df7bfba8a8561587Vendor (CNA)
Linux Linuxfa4f1f52528c73989d820f32bfca06bec5afeeceVendor (CNA)
almalinux:kernel5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.42.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.42.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4611522 days apartblock: add pgmap check to biovec_phys_mergeable
    39Monitor
  • CVE-2026-5322150 days apartip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()
    39Monitor
  • CVE-2026-6403774 days apartwifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled
    39Monitor
  • CVE-2026-6404674 days apartnet: tls: prevent chain-after-chain in plain text SG
    39Monitor
  • CVE-2026-4626628 days apartinet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP
    36Monitor
  • CVE-2026-6410674 days apartKVM: arm64: vgic-its: Reject restored DTE with out-of-range num_eventid_bits
    36Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

nvd-secondary

References

All records