DEBIAN-CVE-2024-47678
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.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Debian:14 | linux | 0, 0 |
| Debian:12 | linux | 6.1.99-1, 6.1.94-1, * |
| Debian:13 | linux | 0, 0 |
| Debian:11 | linux-6.1 | 6.1.106-3, 6.1.106-3, 6.1.112-1 |
| Debian:11 | linux | 5.16.18-1, 5.16.3-1~exp1, 5.16.4-1~exp1 |
Timeline
- Oct 21, 2024 CVE Published
- Apr 28, 2026 CVE Updated