Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.84% (FIRST EPSS); higher than 58.4% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 14b001ba221136c15f894577253e8db535b99487, 3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc, 41d8fdf3afaff312e17466e4ab732937738d5644.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 14b001ba221136c15f894577253e8db535b99487, 3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1cc, 41d8fdf3afaff312e17466e4ab732937738d5644 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

Published
Apr 25, 2024
Updated
Aug 5, 2026
EPSS
0.8% · 58th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26924

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.157
  • linux linux kernel5.16 and later · before 6.1.88
  • linux linux kernel5.6 and later · before 5.10.216
  • linux linux kernel6.7 and later · before 6.8.8
  • linux linux kernel6.2 and later · before 6.6.29
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before e3b887a9c11caf8357a821260e095f2a694a34f2affected · git
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before 7a1679e2d9bfa3b5f8755c2c7113e54b7d42bd46affected · git
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before 41d8fdf3afaff312e17466e4ab732937738d5644affected · git
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before ebf7c9746f073035ee26209e38c3a1170f7b349aaffected · git
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before 14b001ba221136c15f894577253e8db535b99487affected · git
    • 3c4287f62044a90e73a561aa05fc46e62da173da and later · before 3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1ccaffected · git
    • before 5.6not affected · semver
    • 5.10.216 and later · up to and including 5.10.*not affected · semver
    • 5.15.157 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26921Apr 18, 2024 · inet: inet_defrag: prevent sk release while still in use
    22Monitor
  • ← EarlierCVE-2024-26922Apr 23, 2024 · drm/amdgpu: validate the parameters of bo mapping operations more clearly
    22Monitor
  • Later →CVE-2024-26926Apr 25, 2024 · binder: check offset alignment in binder_get_object()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux14b001ba221136c15f894577253e8db535b99487Vendor (CNA)
Linux Linux3cfc9ec039af60dbd8965ae085b2c2ccdcfbe1ccVendor (CNA)
Linux Linux41d8fdf3afaff312e17466e4ab732937738d5644Vendor (CNA)
Linux Linux7a1679e2d9bfa3b5f8755c2c7113e54b7d42bd46Vendor (CNA)
Linux Linuxe3b887a9c11caf8357a821260e095f2a694a34f2Vendor (CNA)
Linux Linuxebf7c9746f073035ee26209e38c3a1170f7b349aVendor (CNA)
almalinux:bpftool4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.27.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.90-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.33.1.150600.12.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)

+27

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records