ipvs: avoid out-of-bounds write in ip_vs_nat_icmp
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 646922a0379496154e8c8faca4f8e2fd9100cacc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipvs: avoid out-of-bounds write in ip_vs_nat_icmp
Sashiko warns that local attacker can modify the packet while it is processed by IPVS. Some places read the IP ihl field multiple times which can cause out-of-bounds access. One such place is ip_vs_nat_icmp where we can write after the validated area.
Fix it by providing ciph argument just like it is done for IPv6 and use ciph->len as offset to the embedded transport header.
Modify some IPv4 header checks by reading the ihl field only once.
From the CVE record · Linux
The Linux kernel's IPVS ICMP NAT code can write out of bounds because it reads the IPv4 header length more than once. A local attacker who can modify a packet while IPVS processes it can trigger the issue; the input does not specify authentication or user-interaction requirements.
Anyone running Linux kernels with IPVS should check their kernel against the vendor advisory; affected versions were not provided.