First published: Mon Oct 21 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux kernel | >=3.18<6.1.113 | |
Linux kernel | >=6.2<6.6.54 | |
Linux kernel | >=6.7<6.10.13 | |
Linux kernel | >=6.11<6.11.2 | |
Linux Kernel | >=3.18<6.1.113 | |
Linux Kernel | >=6.2<6.6.54 | |
Linux Kernel | >=6.7<6.10.13 | |
Linux Kernel | >=6.11<6.11.2 | |
debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.129-1 6.1.135-1 6.12.25-1 6.12.27-1 |
debian/linux-6.1 | 6.1.129-1~deb11u1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-47678 varies depending on the specific configuration and usage context of the affected Linux kernel versions.
To fix CVE-2024-47678, upgrade the Linux kernel to a version that includes the resolution for this vulnerability.
CVE-2024-47678 affects Linux kernel versions between 3.18 and 6.1.113, 6.2 to 6.6.54, 6.7 to 6.10.13, and 6.11 to 6.11.2.
CVE-2024-47678 is a kernel vulnerability related to the improper order of rate limiting for ICMP messages.
As of now, there are no publicly known exploits specifically targeting CVE-2024-47678.