Bug 2466994 (CVE-2026-43114)

Summary: CVE-2026-43114 kernel: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: akhatavk, aos-team-art-private, asdas, dpaolell, jdelft, jupierce, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's netfilter component, specifically within the `nft_set_pipapo_avx2` AVX2 matching functions. This vulnerability occurs when a `pipapo` set with an 'ipv4 . port' key is reloaded. Due to incorrect masking, the system may erroneously identify non-matching elements as duplicates, leading to data integrity issues and unexpected behavior. A remote attacker could potentially exploit this to cause a denial of service or impact data integrity.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-05-06 10:02:17 UTC
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.

Comment 5 errata-xmlrpc 2026-08-26 04:35:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:59723 https://access.redhat.com/errata/RHSA-2026:59723

Comment 6 errata-xmlrpc 2026-09-02 11:02:40 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:62568 https://access.redhat.com/errata/RHSA-2026:62568

Comment 7 errata-xmlrpc 2026-09-02 13:53:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:62638 https://access.redhat.com/errata/RHSA-2026:62638

Comment 8 errata-xmlrpc 2026-09-02 14:00:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:62639 https://access.redhat.com/errata/RHSA-2026:62639

Comment 9 errata-xmlrpc 2026-09-02 14:03:24 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:62642 https://access.redhat.com/errata/RHSA-2026:62642

Comment 10 errata-xmlrpc 2026-09-02 14:07:35 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:62640 https://access.redhat.com/errata/RHSA-2026:62640

Comment 11 errata-xmlrpc 2026-09-02 14:11:37 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:62641 https://access.redhat.com/errata/RHSA-2026:62641

Comment 12 errata-xmlrpc 2026-09-08 00:23:41 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:64767 https://access.redhat.com/errata/RHSA-2026:64767

Comment 13 errata-xmlrpc 2026-09-08 13:15:18 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.22

Via RHSA-2026:63093 https://access.redhat.com/errata/RHSA-2026:63093

Comment 14 errata-xmlrpc 2026-09-09 00:57:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions

Via RHSA-2026:65712 https://access.redhat.com/errata/RHSA-2026:65712

Comment 15 Jon Orris 2026-09-15 09:18:02 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.21

Via RHSA-2026:66351 https://access.redhat.com/errata/RHSA-2026:66351

Comment 16 Jon Orris 2026-09-15 09:21:58 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.20

Via RHSA-2026:66376 https://access.redhat.com/errata/RHSA-2026:66376

Comment 17 Jon Orris 2026-09-16 00:14:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:67721 https://access.redhat.com/errata/RHSA-2026:67721

Comment 18 Jon Orris 2026-09-16 00:42:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:67723 https://access.redhat.com/errata/RHSA-2026:67723

Comment 19 Jon Orris 2026-09-16 06:49:35 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.19

Via RHSA-2026:66370 https://access.redhat.com/errata/RHSA-2026:66370

Comment 22 Jon Orris 2026-10-27 14:10:22 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.18

Via RHSA-2026:89725 https://access.redhat.com/errata/RHSA-2026:89725

Comment 23 Jon Orris 2026-10-27 16:03:43 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.14

Via RHSA-2026:89838 https://access.redhat.com/errata/RHSA-2026:89838

Comment 24 Jon Orris 2026-10-27 17:58:40 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.16

Via RHSA-2026:89714 https://access.redhat.com/errata/RHSA-2026:89714

Comment 25 errata-xmlrpc 2026-11-11 01:43:17 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.13

Via RHSA-2026:95745 https://access.redhat.com/errata/RHSA-2026:95745

Comment 26 errata-xmlrpc 2026-11-11 01:46:34 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.17

Via RHSA-2026:96282 https://access.redhat.com/errata/RHSA-2026:96282

Comment 27 errata-xmlrpc 2026-11-11 12:16:52 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.15

Via RHSA-2026:95755 https://access.redhat.com/errata/RHSA-2026:95755