LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27019: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get()

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() nft_unregister_obj() can concurrent with __nft_obj_type_get(), and there is not any protection when iterate over nf_tables_objects list in __nft_obj_type_get(). Therefore, there is potential data-race of nf_tables_objects list entry. Use list_for_each_entry_rcu() to iterate over nf_tables_objects list in __nft_obj_type_get(), and use rcu_read_lock() in the caller nft_obj_type_get() to protect the entire type query process.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux's nftables subsystem can occur when one process removes an object type while another looks it up. The supplied CVSS assessment rates potential impact as serious, including confidentiality, integrity, and availability loss. Exploitation requires local access and low privileges; the sources provide no evidence of attacks in the wild.

Executive priority

Treat this as a high-priority kernel maintenance issue, especially on multi-user, hosting, container, or development systems where untrusted users may gain local access. It is not documented as remotely exploitable or actively exploited, so prioritize confirmed exposed builds rather than initiating an emergency internet-wide response.

Technical view

The nf_tables object registry could be traversed by __nft_obj_type_get() concurrently with nft_unregister_obj(), without adequate synchronization. The published correction uses RCU-aware list traversal and holds an RCU read lock throughout the type query. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high potential impact.

Likely exposure

Exposure is limited to Linux systems running vulnerable kernel builds with the affected nf_tables code. Internet reachability alone does not enable the documented local attack path. The supplied version data is ambiguous because it flattens introduction and correction boundaries; confirm exposure through distribution advisories or presence of the referenced stable-kernel fix.

Exploitation context

The supplied record does not list this CVE in KEV and provides no evidence of active exploitation or a public working exploit. The CVSS vector indicates a local, low-privilege attack path. Whether the race can be reliably converted into the scored impacts is not established by the supplied sources.

Researcher notes

The defect is an unsynchronized registry-list traversal during concurrent object-type unregistration. The correction protects lookup lifetime using RCU. No CWE is supplied. The affected-version representation is insufficiently clear for precise branch boundaries, and the sources do not establish exploit reliability, prerequisites beyond the CVSS vector, or observed exploitation.

Mitigation direction

  • Install a vendor-supported kernel update containing the referenced nf_tables correction.
  • Check distribution advisories for the corrected package applicable to each kernel branch.
  • Reboot affected systems into the updated kernel after installation.
  • Prioritize systems permitting untrusted or broadly shared local access.
  • Reduce unnecessary local account access while remediation is pending.

Validation and detection

  • Inventory running kernel builds across Linux hosts.
  • Check vendor advisories or package changelogs for CVE-2024-27019 coverage.
  • Confirm the applicable RCU fix is present or vendor-backported.
  • Verify systems are running the updated kernel after reboot.
  • Repeat vulnerability scanning after remediation.
Prepared
Confidence
medium
Sources
8

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-27019 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
2ADP providers
10Source 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-27019Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe50092404c1bc7aaeb0a0f4077fa6f07b073a20f, e50092404c1bc7aaeb0a0f4077fa6f07b073a20f, e50092404c1bc7aaeb0a0f4077fa6f07b073a20f, e50092404c1bc7aaeb0a0f4077fa6f07b073a20f, e50092404c1bc7aaeb0a0f4077fa6f07b073a20f, e50092404c1bc7aaeb0a0f4077fa6f07b073a20funaffected
LinuxLinux4.10, 0, 5.10.219, 5.15.157, 6.1.88, 6.6.29, 6.8.8, 6.9affected
Weakness

CWE details

No CWE listed

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