CVE-2024-27397: netfilter: nf_tables: use timestamp to check for set element timeout
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nftables: 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.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nftables: use timestamp to check for set element timeout
The Linux kernel CVE team has assigned CVE-2024-27397 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050837-CVE-2024-27397-fd1e@gregkh/T
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-27397?
CVE-2024-27397 has a medium severity level as it affects the Linux kernel's netfilter subsystem.
How do I fix CVE-2024-27397?
To fix CVE-2024-27397, upgrade your Linux kernel to the recommended versions, which include 6.7.5, 6.8, or various specified Debian versions.
Which Linux distributions are affected by CVE-2024-27397?
CVE-2024-27397 affects Red Hat and Debian distributions of the Linux kernel.
What components are impacted by CVE-2024-27397?
CVE-2024-27397 impacts the netfilter component of the Linux kernel, specifically in relation to its nf_tables functionality.
Is there a workaround for CVE-2024-27397 if I cannot update immediately?
There are no specified workarounds for CVE-2024-27397; immediate kernel updates are advised for mitigation.