Descrizione
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.
Come correggere
Priorità: Alta — pianificare la correzione entro pochi giorni. Motivazione: CVSS 9.4.
Versioni da aggiornare
- Linux Linux Kernel: vulnerabili le versioni dalla
5.7precedenti alla6.6.136→ aggiornare alla6.6.136o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.7precedenti alla6.12.83→ aggiornare alla6.12.83o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.13precedenti alla6.18.24→ aggiornare alla6.18.24o successiva. - Linux Linux Kernel: vulnerabili le versioni dalla
6.19precedenti alla6.19.14→ aggiornare alla6.19.14o successiva. - Linux Linux Kernel: vulnerabile la versione
7.0 rc1→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.0 rc2→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.0 rc3→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.0 rc4→ installare l'ultima release supportata dal vendor. - Linux Linux Kernel: vulnerabile la versione
7.0 rc5→ installare l'ultima release supportata dal vendor.
Patch e advisory
- Patch: git.kernel.org/stable/c/07de44424bb7f17ef9357e8535d…
- Patch: git.kernel.org/stable/c/0abbc43f71d99baadeeba6fa3fe…
- Patch: git.kernel.org/stable/c/3d53f9aafd469ae1ea27051e00f…
- Patch: git.kernel.org/stable/c/d3c0037ffe1273fa1961e779ff6…
- Patch: git.kernel.org/stable/c/fa4f1f52528c73989d820f32bfc…
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Ridurre l'esposizione del componente vulnerabile (segmentazione, accesso solo da reti fidate) finché la patch non è applicata.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Linux | Linux Kernel | ≥ 5.7 < 6.6.136 | 6.6.136 |
| Linux | Linux Kernel | ≥ 6.7 < 6.12.83 | 6.12.83 |
| Linux | Linux Kernel | ≥ 6.13 < 6.18.24 | 6.18.24 |
| Linux | Linux Kernel | ≥ 6.19 < 6.19.14 | 6.19.14 |
| Linux | Linux Kernel | 7.0 rc1 | — |
| Linux | Linux Kernel | 7.0 rc2 | — |
| Linux | Linux Kernel | 7.0 rc3 | — |
| Linux | Linux Kernel | 7.0 rc4 | — |
| Linux | Linux Kernel | 7.0 rc5 | — |
Riferimenti
- Patchhttps://git.kernel.org/stable/c/07de44424bb7f17ef9357e8535df96d9e97c40cb
- Patchhttps://git.kernel.org/stable/c/0abbc43f71d99baadeeba6fa3fe1c80b676f57ed
- Patchhttps://git.kernel.org/stable/c/3d53f9aafd469ae1ea27051e00f5b96ca1b55d52
- Patchhttps://git.kernel.org/stable/c/d3c0037ffe1273fa1961e779ff6906234d6cf53c
- Patchhttps://git.kernel.org/stable/c/fa4f1f52528c73989d820f32bfca06bec5afeece
- Riferimentohttps://git.kernel.org/stable/c/1c43f0dd8691ddf8884793b481ddc7511cf593c3
- Riferimentohttps://git.kernel.org/stable/c/c7babe2f28b507e17f28e9f753b7caec72d4857f
- Riferimentohttps://git.kernel.org/stable/c/f8c39983fc9c1a978c82e6f2df7bfba8a8561587
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:59723
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62568
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62638
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62639
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62640
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62641
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:62642
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:63093
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:64767
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:65712
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:66351
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:66370
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:66376
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:67721
- Riferimentohttps://access.redhat.com/errata/RHSA-2026:67723
- Riferimentohttps://access.redhat.com/security/cve/CVE-2026-43114
- Riferimentohttps://bugzilla.redhat.com/show_bug.cgi?id=2466994