CVE-2025-38678
BaseFortify
Publication date: 2025-09-03
Last updated on: 2025-12-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's netfilter nf_tables component allows a chain or flowtable update to include duplicated devices within the same batch. When this happens, the netdev event path only removes the first instance of the duplicated device, leaving the hook of the duplicated device unregistered. This can cause warnings during hook unregistration and potentially inconsistent state in the netfilter hooks.
How can this vulnerability impact me? :
The impact of this vulnerability includes potential warnings and instability in the netfilter subsystem of the Linux kernel due to unregistered hooks from duplicated devices. This could lead to unexpected behavior in network filtering or firewall rules, possibly affecting network security or reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for warnings related to nf_hook_entry_head, specifically messages like: "WARNING: CPU: ... at net/netfilter/core.c:340 nf_hook_entry_head". You can use commands such as 'dmesg | grep nf_hook_entry_head' or 'journalctl -k | grep nf_hook_entry_head' to find these warnings indicating the presence of duplicated devices in netfilter updates.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that your Linux kernel is updated to a version where the issue is resolved. The fix involves checking for duplicated devices in the transaction batch and aborting the update if duplicates exist. Until you update, monitor for the warning messages and avoid applying chain/flowtable updates that may include duplicated devices in the same batch.