netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 720344340fb9be2765bbaab7b292ece0a4570eae · < a34ba4bdeec0c3b629160497594908dc820110f1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path
The commit mutex should not be released during the critical section between nft_gc_seq_begin() and nft_gc_seq_end(), otherwise, async GC worker could collect expired objects and get the released commit lock within the same GC sequence.
nf_tables_module_autoload() temporarily releases the mutex to load module dependencies, then it goes back to replay the transaction again. Move it at the end of the abort phase after nft_gc_seq_end() is called.
From the CVE record · Linux
The Linux kernel's nf_tables abort path can release the commit mutex before a garbage-collection sequence ends. This can allow an asynchronous garbage-collection worker to acquire the lock and collect expired objects during that sequence. The input does not specify attacker access, authentication, or user-interaction requirements.
Engineers running Linux kernels with nf_tables should check their deployments; affected versions are not specified.