CVE-2024-47678: Linux kernel · icmp: change the order of rate limits ICMP messages are ratelimited :
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.4 Critical · fixed in 6.8.0-1023.25~22.04.1 : patch Linux kernel as a priority.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 6.8.0-1023.25~22.04.1, 6.8.0-1025.30~22.04.1, 6.8.0-1024.26~22.04.1 +29
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7311-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7384-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7385-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7386-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-47678 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-47678 (opens in a new tab)
- git.kernel.org/linus/8c2bd38b95f75f3d2a08c93e35303e26d480d24e (opens in a new tab)
- git.kernel.org/stable/c/997ba8889611891f91e8ad83583466aeab6239a3 (opens in a new tab)
- git.kernel.org/stable/c/662ec52260cc07b9ae53ecd3925183c29d34288b (opens in a new tab)
- git.kernel.org/stable/c/a7722921adb046e3836eb84372241f32584bdb07 (opens in a new tab)
- git.kernel.org/stable/c/483397b4ba280813e4a9c161a0a85172ddb43d19 (opens in a new tab)
- git.kernel.org/stable/c/8c2bd38b95f75f3d2a08c93e35303e26d480d24e (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7311-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7384-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7385-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7386-1 (opens in a new tab)