CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates
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
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can leave a netfilter hook in an inconsistent state when a device is duplicated during a ruleset update. A local low-privileged actor may trigger the vulnerable operation without user interaction. The supplied CVSS rating indicates potentially serious confidentiality, integrity, and availability impact, although the bundle documents a kernel warning rather than a demonstrated compromise.
Executive priority
Prioritize assessment and patching as a high-severity local kernel issue, especially on shared Linux infrastructure. Internet exposure alone does not establish reachability. Require platform owners to verify vendor backports and local access conditions. Escalate urgently if untrusted users can exercise nf_tables operations; otherwise remediate through the normal high-priority kernel maintenance process.
Technical view
During an nf_tables chain or flowtable update, duplicate devices can enter the same transaction batch. The netdev event path removes only the first matching device, leaving the duplicate device's hook unregistered and triggering a warning during hook removal. The kernel fix rejects duplicate devices in the transaction with EEXIST.
Likely exposure
The bundle marks Linux as affected and lists 5.8, 5.10.247, 5.15.197, 6.1.159, 6.6.117, 6.12.59, 6.16.2, and 6.17. Exact affected ranges are not clearly expressed. Exposure requires local, low-privileged access to the vulnerable nf_tables update path. Confirm distribution kernel versions and backports rather than relying only on upstream version numbers.
Exploitation context
The CVSS vector is local, low complexity, low privilege, and requires no user interaction. The supplied record does not establish active exploitation, and the CVE is not identified as being in KEV. No public proof of exploitation is included. Treat the stated high confidentiality, integrity, and availability impacts as rating data, not demonstrated outcomes.
Researcher notes
The source establishes a duplicate-device transaction flaw, incomplete hook cleanup, and an upstream rejection fix. It does not explain how the warning produces the CVSS-rated confidentiality, integrity, and availability consequences. The affected-version presentation is ambiguous and includes a repeated commit identifier under an unaffected entry. Branch-specific fix commits should be matched against each deployed kernel's ancestry or vendor changelog.
Mitigation direction
Update to a vendor-supported kernel containing the applicable stable fix.
Check distribution security guidance for backported fixes and precise affected package versions.
Restrict unnecessary local access to nf_tables administration until remediation is confirmed.
Prioritize shared or multi-user Linux systems where untrusted local users can reach netfilter functionality.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Confirm the installed package includes the relevant upstream fix or vendor backport.
Identify users and workloads able to perform nf_tables chain or flowtable updates.
Review kernel logs for related nf_hook_entry_head warnings, without treating absence as proof of safety.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38678 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.