icmp: change the order of rate limits
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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 :
From the CVE record · Linux
The Linux kernel applies its host-wide ICMP rate limit before the per-destination limit, creating a potential side channel. The issue concerns network ICMP handling; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels affected by the ICMP rate-limit ordering issue should check their versions; affected versions are not listed in the input.