Review reviewCritical

CVE-2026-43114

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

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

CVSS
9.4
EPSS
0.36%
28.3% percentile
CISA KEV
Not listed
Published
2026.05.06
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.36%
Technical severityCVSS 9.4

Vulnerability overview

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

Affected product and versions

Product
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6
Affected versions
>= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < f8c39983fc9c1a978c82e6f2df7bfba8a8561587, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < c7babe2f28b507e17f28e9f753b7caec72d4857f, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < 1c43f0dd8691ddf8884793b481ddc7511cf593c3, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < fa4f1f52528c73989d820f32bfca06bec5afeece, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < 3d53f9aafd469ae1ea27051e00f5b96ca1b55d52, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < 07de44424bb7f17ef9357e8535df96d9e97c40cb, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < 0abbc43f71d99baadeeba6fa3fe1c80b676f57ed, >= 7400b063969bdca4a06cd97f1294d765c8eecbe1 < d3c0037ffe1273fa1961e779ff6906234d6cf53c, >= 5.7, >= 5.7 < 6.6.136, >= 6.7 < 6.12.83, >= 6.13 < 6.18.24, >= 6.19 < 6.19.14, 7.0
Fixed versions
6.6.136, 6.12.83, 6.18.24, 6.19.14

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CWE
CWE-480
CVE-2026-43114 — Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 | SECUFOCUS NOW