netfilter: nf_tables: don't skip expired elements during walk
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d0982927e79049675cb6c6c04a0ebb3dad5a434 · < bd156ce9553dcaf2d6ee2c825d1a5a1718e86524| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: don't skip expired elements during walk
There is an asymmetry between commit/abort and preparation phase if the following conditions are met:
1. set is a verdict map ("1.2.3.4 : jump foo") 2. timeouts are enabled
In this case, following sequence is problematic:
1. element E in set S refers to chain C 2. userspace requests removal of set S 3. kernel does a set walk to decrement chain->use count for all elements from preparation phase 4. kernel does another set walk to remove elements from the commit phase (or another walk to do a chain->use increment for all elements from abort phase)
If E has already expired in 1), it will be ignored during list walk, so its use count won't have been changed.
Then, when set is culled, ->destroy callback will zap the element via nf_tables_set_elem_destroy(), but this function is only safe for elements that have been deactivated earlier from the preparation phase: lack of earlier deactivate removes the element but leaks the chain use count, which results in a WARN splat when the chain gets removed later, plus a leak of the nft_chain structure.
From the CVE record · Linux
The Linux kernel’s nf_tables can mishandle expired elements when removing a verdict-map set with timeouts enabled. This can leak a chain reference and nft_chain structure, produce a warning when the chain is later removed, and cause flush commands to report erroneous ENOENT errors. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels that use nf_tables verdict-map sets with timeouts should check their systems; affected versions are not specified.