netfilter: nft_set_pipapo: release elements in clone only from destroy path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e · < 9384b4d85c46ce839f51af01374062ce6318b2f2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_set_pipapo: release elements in clone only from destroy path
Clone already always provides a current view of the lookup table, use it to destroy the set, otherwise it is possible to destroy elements twice.
This fix requires:
212ed75dc5fb ("netfilter: nf_tables: integrate pipapo into commit protocol")
which came after:
9827a0e6e23b ("netfilter: nft_set_pipapo: release elements in clone from abort path").
From the CVE record · Linux
The Linux kernel's netfilter nft_set_pipapo code can destroy set elements twice when destroying a set. The input does not specify how an attacker could trigger this, whether access is local or over a network, or whether authentication or user interaction is required.
Engineers running Linux kernels with the affected netfilter nft_set_pipapo code should check their kernel; affected versions are not specified.