LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26673: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations - Disallow families other than NFPROTO_{IPV4,IPV6,INET}. - Disallow layer 4 protocol with no ports, since destination port is a mandatory attribute for this object.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects netfilter connection tracking expectations. The fix adds input validation so unsupported network families and layer 4 protocols without ports cannot be used in custom expectations. Business urgency is hard to rank because the source bundle provides no CVSS score, impact statement, or exploitation evidence.

Executive priority

Handle as a kernel patch-management item with uncertain severity. Prioritize internet-facing, multi-tenant, firewall, routing, Kubernetes node, and security appliance systems first. Escalate only if your vendor advisory assigns higher severity or confirms practical exploitation.

Technical view

CVE-2024-26673 is resolved in Linux kernel netfilter nft_ct by sanitizing layer 3 family and layer 4 protocol values for custom expectations. The patch disallows families outside IPv4, IPv6, and INET, and rejects layer 4 protocols with no ports because destination port is mandatory for this object.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with netfilter/nftables connection tracking expectation functionality available. The bundle lists Linux kernel ranges including 5.3 through fixed stable updates around 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, and 6.8.

Exploitation context

The bundle does not include exploit details, public exploitation reports, or CISA KEV listing. Treat active exploitation as unconfirmed. The available evidence supports a kernel input-validation flaw in a networking subsystem, not a proven internet-scale exploitation campaign.

Researcher notes

The strongest source evidence is the kernel fix description, which identifies missing protocol-family and layer 4 protocol validation in nft_ct expectations. The bundle lacks crash, privilege, confidentiality, or availability impact details, so validation should focus on patch presence and subsystem exposure rather than assumed exploitability.

Mitigation direction

  • Update Linux kernels using vendor packages containing the referenced stable fixes.
  • Prioritize hosts using nftables, netfilter, or connection tracking features.
  • Review Debian LTS guidance if operating Debian long-term support systems.
  • Check distribution advisories before applying non-vendor kernels.
  • Track kernel updates through normal emergency change controls if exposure is confirmed.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, containers hosts, and cloud images.
  • Compare deployed kernels with affected and fixed versions from vendor advisories.
  • Confirm whether nftables, netfilter, or conntrack expectation features are in use.
  • Verify patched systems include one of the referenced stable kernel fixes.
  • Record any unsupported kernels requiring compensating operational action.
Prepared
Confidence
medium
Sources
10

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-26673 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1, 857b46027d6f91150797295752581b7155b9d0e1unaffected
LinuxLinux5.3, 0, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, 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.