netfilter: nf_tables: reject duplicate device on updates
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 78d9f48f7f44431a25da2b46b3a8812f6ff2b981 · < d7615bde541f16517d6790412da6ec46fa8a4c1f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: reject duplicate device on updates
A chain/flowtable update with duplicated devices in the same batch is possible. Unfortunately, netdev event path only removes the first device that is found, leaving unregistered the hook of the duplicated device.
Check if a duplicated device exists in the transaction batch, bail out with EEXIST in such case.
WARNING is hit when unregistering the hook:
[49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S 6.16.0+ #170 PREEMPT(full) [...] [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150
From the CVE record · Linux
Linux kernel nf_tables allows a chain or flowtable update to include duplicate devices in the same batch. When a device is unregistered, the netdev event path removes only the first match, leaving a hook registered and triggering a kernel warning when that hook is unregistered. The report shows a local nft process; it does not specify authentication requirements or user interaction.
Engineers running Linux kernels with nf_tables should check their systems; affected versions are not specified.