Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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").

Timeline

  1. ID reserved

    By Linux

  2. · 45 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26809, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 4a6430b99f67842617c7208ca55a411e903ba03a – < b36b83297ff4910dfc8705402c8abffd4bbf8144
    • affected 5ccecafc728b0df48263d5ac198220bcd79830bc – < 362508506bf545e9ce18c72a2c48dcbfb891ab9c
    • affected 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e – < 5ad233dc731ab64cdc47b84a5c1f78fff6c024af
    • affected 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e – < ff90050771412b91e928093ccd8736ae680063c2
    • affected 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e – < 821e28d5b506e6a73ccc367ff792bd894050d48b
    • affected 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e – < 9384b4d85c46ce839f51af01374062ce6318b2f2
    • affected 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e – < b0e256f3dd2ba6532f37c5c22e07cb07a36031ee
    • affected d2b18d110685ce46ca1633b8ec586c685e243a51
    • affected 5.10.130 – < 5.10.214
    • affected 5.15.54 – < 5.15.153
    • affected 5.18.11 – < 5.19
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 5.10.214 – ≤ 5.10.*
    • unaffected 5.15.153 – ≤ 5.15.*
    • unaffected 6.1.83 – ≤ 6.1.*
    • unaffected 6.6.23 – ≤ 6.6.*
    • unaffected 6.7.11 – ≤ 6.7.*
    • unaffected 6.8.2 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26809 badge
[![CVE-2024-26809](https://cveledger.app/badge/CVE-2024-26809.svg)](https://cveledger.app/cve/CVE-2024-26809)

Record last updated .