# CVE-2024-47678: icmp: change the order of rate limits

> Attackers can exploit ICMP rate limiting order to perform side-channel attacks, potentially disclosing sensitive information.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Oct 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-50716, AZL-50979, BELL-CVE-2024-47678, DEBIAN-CVE-2024-47678, GHSA-522v-vw33-wcv7, ROOT-OS-DEBIAN-11-CVE-2024-47678, ROOT-OS-UBUNTU-2204-CVE-2024-47678, UBUNTU-CVE-2024-47678

## What is CVE-2024-47678?

CVE-2024-47678 is a critical vulnerability in Linux kernel, published on 21 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

icmp: change the order of rate limits

ICMP messages are ratelimited :

After the blamed commits, the two rate limiters are applied in this order:

1) host wide ratelimit (icmp_global_allow())

2) Per destination ratelimit (inetpeer based)

In order to avoid side-channels attacks, we need to apply
the per destination check first.

This patch makes the following change :

1) icmp_global_allow() checks if the host wide limit is reached.
   But credits are not yet consumed. This is deferred to 3)

2) The per destination limit is checked/updated.
   This might add a new node in inetpeer tree.

3) icmp_global_consume() consumes tokens if prior operations succeeded.

This means that host wide ratelimit is still effective
in keeping inetpeer tree small even under DDOS.

As a bonus, I removed icmp_global.lock as the fast path
can use a lock-free operation.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2024-47678?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-47678?

Apply the vendor's patch.

## Is CVE-2024-47678 being exploited?

There is no known exploitation of CVE-2024-47678 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47678 and fix it if it is affected.

What it is: CVE-2024-47678 is a critical vulnerability in Linux kernel, published on 21 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47678 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47678/ (Markdown: https://insights.sbomify.com/CVE-2024-47678/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47678
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47678
- OSV: https://osv.dev/vulnerability/CVE-2024-47678

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47678/
Summaries are generated and may contain mistakes; the official description above is the record.