LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26809: netfilter: nft_set_pipapo: release elements in clone only from destroy path

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: release elements in clone only from destroy path Clone already always provides a current view of the lookup table, use it to destroy the set, otherwise it is possible to destroy elements twice. This fix requires: 212ed75dc5fb ("netfilter: nf_tables: integrate pipapo into commit protocol") which came after: 9827a0e6e23b ("netfilter: nft_set_pipapo: release elements in clone from abort path").

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26809 is a Linux kernel netfilter issue in nftables pipapo set handling. The kernel could attempt to destroy the same set elements twice, creating a kernel memory-safety risk. The sources do not provide CVSS, CWE, or confirmed exploit activity.

Executive priority

Treat this as a kernel patch-management item with uncertain severity. It is not KEV-listed in the bundle, but kernel memory-safety bugs can have high operational impact, so include it in the next normal or accelerated Linux update cycle based on asset criticality.

Technical view

The fix changes nft_set_pipapo clone element release behavior so elements are released only from the destroy path. The CVE notes this depends on earlier nf_tables pipapo commit-protocol integration. Multiple Linux stable commits and a Debian LTS advisory are referenced.

Likely exposure

Systems running affected Linux kernels with nf_tables/netfilter functionality may be exposed. Practical exposure depends on kernel version, distribution backports, and whether vulnerable code is reachable in the deployed configuration.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. It also does not provide public exploit details, required privileges, or attack preconditions, so exploitability should be treated as unresolved from these sources.

Researcher notes

Evidence supports a double-destroy condition in nft_set_pipapo clone handling, fixed through Linux stable commits. The bundle lacks CVSS, CWE, exploitability details, and privilege requirements. Validate against downstream backports rather than relying only on upstream version numbers.

Mitigation direction

  • Apply Linux kernel updates from your distribution or kernel vendor.
  • Prioritize updates that include the referenced stable netfilter fixes.
  • Review Debian LTS guidance if running Debian LTS kernels.
  • Track vendor advisories for exact package versions and backports.
  • Avoid inventing compensating controls without vendor confirmation.

Validation and detection

  • Inventory running kernel versions across Linux systems.
  • Check vendor advisories for whether each kernel build includes the fix.
  • Confirm nftables/netfilter usage on exposed hosts.
  • Verify rebooted systems are running the updated kernel.
  • Document unresolved systems for risk acceptance or remediation tracking.
Prepared
Confidence
medium
Sources
10

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-26809 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4a6430b99f67842617c7208ca55a411e903ba03a, 5ccecafc728b0df48263d5ac198220bcd79830bc, 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e, 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e, 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e, 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e, 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e, d2b18d110685ce46ca1633b8ec586c685e243a51, 5.10.130, 5.15.54, 5.18.11unaffected
LinuxLinux5.19, 0, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 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.