netfilter: nf_tables: adapt set backend to use GC transaction API
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9d0982927e79049675cb6c6c04a0ebb3dad5a434 · < e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: adapt set backend to use GC transaction API
Use the GC transaction API to replace the old and buggy gc API and the busy mark approach.
No set elements are removed from async garbage collection anymore, instead the _DEAD bit is set on so the set element is not visible from lookup path anymore. Async GC enqueues transaction work that might be aborted and retried later.
rbtree and pipapo set backends does not set on the _DEAD bit from the sync GC path since this runs in control plane path where mutex is held. In this case, set elements are deactivated, removed and then released via RCU callback, sync GC never fails.
From the CVE record · Linux
The Linux kernel's nf_tables set backends used a buggy garbage-collection API. The input does not specify what an attacker could do or whether exploitation requires local or network access, authentication, or user interaction.
Engineers running Linux kernels with nf_tables should check their versions; affected versions are not specified.