CVE-2024-27397
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk17th percentile - higher than 17% of all known CVEs
Summary
A vulnerability has been identified in the Linux kernel's netfilter module regarding the use of a timestamp to check for set element expiration. A timestamp field has been added at the beginning of the transaction to avoid an element expiring while the control plane transaction is still ongoing.
Risk Assessment
This vulnerability may lead to unintended expiration of set elements, potentially affecting firewall rules and network security. Organizations should be aware of potential security gaps related to time management in transactions.
Recommendation
It is recommended to update the Linux kernel to the latest version to patch this vulnerability and to monitor netfilter configurations to ensure that set elements do not expire during active transactions.
Other vulnerabilities in Linux kernel, netfilter
See all- CVE-2024-27065High
A vulnerability in the Linux kernel has been resolved in netfilter, which involved improper comparison of internal table flags during updates. This issue has been fixed by restoring the skipping of transactions if the table update does not modify flags.
- CVE-2026-45860High
A vulnerability in the Linux kernel's netfilter module has been resolved regarding the connection clean-up limit. Fixes have been implemented to increase the clean-up limit to 64 connections and optimize the process of collecting unused connections.
- CVE-2026-43116High
A vulnerability has been identified in the Linux kernel within the netfilter module regarding safe access to the master conntrack object. The issue arises because this object can disappear, leading to invalid access.
- CVE-2023-4147High
A use-after-free flaw was found in the Linux kernel’s Netfilter functionality when adding a rule with NFTA_RULE_CHAIN_ID. This flaw allows a local user to crash or escalate their privileges on the system.
- CVE-2023-4004High
A use-after-free flaw was found in the Linux kernel's netfilter related to triggering the nft_pipapo_remove function without the NFT_SET_EXT_KEY_END element. This could lead to system crashes or privilege escalation by a local user.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: use timestamp to check for set element timeout Add a timestamp field at the beginning of the transaction, store it in the nftables per-netns area. Update set backend .insert, .deactivate and sync gc path to use the timestamp, this avoids that an element expires while control plane transaction is still unfinished. .lookup and .update, which are used from packet path, still use the current time to check if the element has expired. And .get path and dump also since this runs lockless under rcu read size lock. Then, there is async gc which also needs to check the current time since it runs asynchronously from a workqueue.