CVE-2024-27397
Last modified
CVE-2024-27397 is a high-severity vulnerability rated 7/10 on the CVSS scale. 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. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.1, < 4.19.320 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.282 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.224 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.165 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.97 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.84 | — |
| Linux | Linux Kernel | >= 6.7, < 6.7.5 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-27397?
How severe is CVE-2024-27397?
How do I fix CVE-2024-27397?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-27391In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27392In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27393In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2024-27394In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27395In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27396In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27398In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27399In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2740Information exposure vulnerability in Planet IGS-4215-16T2S,…7.7
- CVE-2024-27400In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27401In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-27402In the Linux kernel, the following vulnerability has been re…5.8
Are you affected by CVE-2024-27397?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
