Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2024-57947

A flaw in the Linux kernel’s netfilter nf_set_pipapo component allowed incorrect matching of packet filtering sets. The bug caused bits from a smaller field to leak into future rounds, potentially letting attackers bypass or misdirect traffic. The issue has been fixed in a kernel patch.

publishedJan 23, 2025
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
10th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel (netfilter nf_set_pipapo) – all distributions using the affected kernel version.

02

Real-world impact

An attacker could craft packets that exploit the faulty set matching, allowing traffic to slip through firewall rules or be redirected to unintended destinations, compromising confidentiality, integrity, and availability of network services.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability requires no authentication or user interaction, yet it can fully compromise confidentiality, integrity, and availability of the affected system.

04

What to do about it

official fix available
recommended steps
  1. 011. Verify your current Linux kernel version.
  2. 022. Update to the latest kernel release that includes the netfilter nf_set_pipapo fix (e.g., via your distribution’s package manager).
  3. 033. Reboot the system to load the updated kernel.

NVD description indicates the vulnerability has been resolved

05

Timeline

  1. Jan 23, 2025 · Jan 23, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →