ipv4: validate checksum_start before completing checksum
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f43798c27684ab925adde7d8acc34c78c6e50df8 · < f3e835af6226f1dd12160cbd696081e9b6155de0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipv4: validate checksum_start before completing checksum
If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can corrupt the network header and cause a bunch of mischief.
This was discovered and reported by Paulos, and has been reporoduced by others independently since.
We really shouldn't allow such packets in, but as a defence in depth measure, let's also check before we complete the checksum.
A more complete validation at input is forthcoming, but needs more work.
From the CVE record · Linux
The Linux kernel’s IPv4 stack can corrupt a packet’s network header when a packet with bad checksum metadata reaches checksum completion. The input does not establish how an attacker could introduce such a packet, whether authentication or user interaction is required, or the resulting impact beyond header corruption.
Engineers running the Linux kernel should check whether their version is affected; no affected versions are specified.