CVE-2026-43114

Aliases:UBUNTU-CVE-2026-43114DEBIAN-CVE-2026-43114CGA-2f8j-qwrc-jjvmCGA-92vv-j925-q62jCGA-fpcj-cjjm-chfgCGA-hj62-h2rc-g8v6CGA-mg9x-mh2v-94m9CGA-rmgc-73g8-9q9v
Advisory lineage Upstream: 0 Downstream: 32
Modified
Published: 06 May 2026, 07:40
Last modified:17 Sept 2026, 12:04

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.4 CRITICAL
v3.1 (cve.org)
EPSS Score
0.37% LOW
0% probability +0.01%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

06 May 2026, 07:40
Published
Vulnerability first disclosed
17 Sept 2026, 12:04
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v4.0•MEDIUM•Score: 6.3CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
  • v3.1•CRITICAL•Score: 9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

EPSS Trends

Current EPSS score: 0.37%• Percentile: 31%

Techniques & Countermeasures

  • CWE-480•Use of Incorrect Operator

    The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.

Affected Systems

  • chainguard•linux-aws-6.18

    < 6.18.31-r0

  • chainguard•linux-azure-6.18

    < 6.18.24-r1

  • chainguard•linux-gcp-6.18

    < 6.18.31-r0

  • chainguard•linux-qemu-6.18

    < 6.18.31-r0

  • chainguard•linux-qemu-6.18-bootc-boot-installed

    < 6.18.31-r0

  • chainguard•linux-vmware-6.18

    < 6.18.24-r1

  • debian•linux

    < 5.10.259-1 | < 6.1.176-1 | < 6.12.85-1 | < 6.19.14-1

  • debian•linux-6.1

    < 6.1.176-1~deb11u1

  • ubuntu•linux

    < 5.15.0-185.195 | < 6.8.0-134.134 | < 6.17.0-40.40

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    < 5.15.0-1111.118 | < 6.8.0-1060.63 | < 6.17.0-1019.19

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.15

    < 5.15.0-1111.118~20.04.1

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.14

    all

  • ubuntu•linux-aws-6.17

    < 6.17.0-1019.19~24.04.1

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-6.5

    all

  • ubuntu•linux-aws-6.8

    < 6.8.0-1060.63~22.04.1

  • ubuntu•linux-aws-fips

    all | < 5.15.0-1111.118+fips1 | < 6.8.0-1060.63+fips1

  • ubuntu•linux-azure

    all | < 5.15.0-1116.125 | < 6.8.0-1063.71 | all

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.15

    < 5.15.0-1116.125~20.04.1

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.11

    all

  • ubuntu•linux-azure-6.14

    all

  • ubuntu•linux-azure-6.17

    < 6.17.0-1021.21~24.04.1

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-6.5

    all

  • ubuntu•linux-azure-6.8

    < 6.8.0-1063.71~22.04.1

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all | all | < 6.8.0-1062.69 | all | all

  • ubuntu•linux-azure-fde-5.15

    < 5.15.0-1116.125~20.04.1

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.14

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fde-6.8

    < 6.8.0-1062.69~22.04.1

  • ubuntu•linux-azure-fde-7.0

    all

  • ubuntu•linux-azure-fips

    all | < 5.15.0-1116.125+fips1 | < 6.8.0-1062.69+fips1

  • ubuntu•linux-azure-nvidia

    all

  • ubuntu•linux-azure-nvidia-6.14

    all

  • ubuntu•linux-bluefield

    all | < 5.15.0-1095.97 | < 6.8.0-1026.30

  • ubuntu•linux-fips

    all | < 5.15.0-185.195+fips1 | < 6.8.0-134.134+fips1

Showing first 50 affected entries in server-rendered view.

References (59)