LiveActive security incident?Get immediate response
CVE Record

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

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing flaw in Linux nftables can let a set element expire before a control-plane transaction finishes. This inconsistent state carries a high 7.8 local-attack rating and could affect confidentiality, integrity, and availability. An attacker needs local, low-privileged access; the bundle does not establish remote exploitation.

Executive priority

Prioritize remediation on shared Linux systems or other hosts where untrusted users have local access. Schedule remaining affected systems through normal high-severity patching. Emergency internet-edge action is not supported by the supplied evidence because the attack vector is local and active exploitation is unconfirmed.

Technical view

nf_tables checked set-element timeouts against changing current time during insertion, deactivation, and synchronous garbage collection. An element could therefore expire mid-transaction. The fix records a transaction-start timestamp in per-network-namespace nftables state. Packet lookup/update, get/dump, and asynchronous garbage collection continue using current time.

Likely exposure

Exposure is limited to Linux kernels containing the vulnerable nf_tables code. The bundle lists affected releases from 4.1 through 6.8, including several stable-series builds, but its flattened version data does not define precise ranges. Confirm exposure using the running build and applicable distributor advisory.

Exploitation context

The KEV flag is false, and the supplied sources do not report active exploitation or a public exploit. CVSS specifies a local attack vector, low complexity, low privileges, and no user interaction. The evidence does not support characterizing this vulnerability as remotely exploitable.

Researcher notes

The bundle does not identify a CWE or explain the concrete memory-safety consequence, trigger prerequisites, or exact downstream version ranges. Focus analysis on transaction-time consistency around expiring nftables set elements. Do not infer use-after-free or privilege escalation without additional evidence.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable referenced Linux stable fix or downstream backport.
  • Follow the operating-system or appliance vendor advisory for exact corrected package versions.
  • Restrict untrusted local access while awaiting remediation; this reduces risk but does not correct the flaw.
  • Ensure the remediated kernel is running after maintenance.

Validation and detection

  • Record each system's running kernel build and compare it with the distributor's affected and corrected versions.
  • Determine whether nftables and the nf_tables subsystem are present or enabled.
  • Verify the kernel includes the applicable stable commit or a documented downstream backport.
  • After maintenance, confirm the corrected kernel is running and repeat vulnerability inventory.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-27397 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-27397Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251d, c3e1b005ed1cc068fc9d454a6e745830d55d251dunaffected
LinuxLinux4.1, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.97, 6.6.84, 6.7.5, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.