netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7400b063969bdca4a06cd97f1294d765c8eecbe1 · < 07de44424bb7f17ef9357e8535df96d9e97c40cb| No fix yet |
| Linux Linux |
|
|
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:
From the CVE record · Linux
The Linux kernel’s AVX2 pipapo set matching can return a non-matching element after a set is flushed. This can cause a false element-clash error when the set is reloaded. The input does not establish an attacker action, access requirement, or user-interaction requirement.
Engineers running Linux kernels that use AVX2 pipapo set matching should check their installations; affected versions are not specified.