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

CVE-2024-47678

A flaw in the Linux kernel’s ICMP rate‑limiting logic could let an attacker send large numbers of ICMP packets to a host. The bug was fixed by reordering the rate‑limit checks so that per‑destination limits are applied before the host‑wide limit. The patch also removed an unnecessary lock for better performance.

publishedOct 21, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.4
critical · how bad it is
exploitation · epss
<1%
15th 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

All Linux kernel users, regardless of distribution, are affected until they upgrade to a kernel version that includes the patch.

02

Real-world impact

An attacker could flood a target with ICMP packets, potentially exhausting resources or causing a denial‑of‑service condition. Because the flaw does not require authentication, anyone on the network could exploit it.

03

Why this severity

The CVSS score of 9.4 reflects that the vulnerability is exploitable over the network (AV:N), requires no privileges (PR:N), and has no user interaction (UI:N). It can lead to high confidentiality and integrity impact by allowing an attacker to send arbitrary ICMP traffic, while the availability impact is considered low because the host‑wide limit still protects the system from total exhaustion.

04

What to do about it

official fix available
recommended steps
  1. 01Update the Linux kernel to a version that includes the patch that reorders ICMP rate limiting.
  2. 02Reboot the system to load the new kernel.

NVD description indicates patch applied

05

Timeline

  1. Oct 21, 2024 · Oct 21, 2024
    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 impactLow
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 →