7.8

CVE-2024-26924: netfilter: nft_set_pipapo: do not free live element

Modified
AliasesUBUNTU-CVE-2024-26924USN-6863-1DEBIAN-CVE-2024-26924
Published 24-04-2024Last modified 05-08-2026

Vulnerability summary

CVE-2024-26924 is a high (CVSS 7.8) NULL Pointer Dereference vulnerability in debian debian_linux. EPSS estimates a 0.85% chance of exploitation in the next 30 days, higher than 58.1% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.85%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 46 · Related 38

Timeline

  1. 24-04-2024
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem("00000000") timeout 100 ms ... add_elem("0000000X") timeout 100 ms del_elem("0000000X") <---------------- delete one that was just added ... add_elem("00005000") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.85%

Chance of exploitation in the next 30 days

Percentile

58%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.85% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu109 products
  • linux< 5.15.0-113.123 | < 6.8.0-36.36
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1064.70 | < 6.8.0-1010.10
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
Linux2 products
  • linux≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < e3b887a9c11caf8357a821260e095f2a694a34f2 | ≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < 7a1679e2d9bfa3b5f8755c2c7113e54b7d42bd46 | ≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < 41d8fdf3afaff312e17466e4ab732937738d5644 | ≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < ebf7c9746f073035ee26209e38c3a1170f7b349a | ≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < 14b001ba221136c15f894577253e8db535b99487 | ≥ 3c4287f62044a90e73a561aa05fc46e62da173da, < 3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc | 5.6
  • linux_kernel≥ 5.6, < 5.10.216 | ≥ 5.11, < 5.15.157 | ≥ 5.16, < 6.1.88 | ≥ 6.2, < 6.6.29 | ≥ 6.7, < 6.8.8 | 6.9:rc1 | 6.9:rc2 | 6.9:rc3 | 6.9:rc4

3 vendors · 113 products

References

33 links
Show all 33 references