ipvs: fix reversed sequence option serialization
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 986a075795339c5ea1122ce9290dfd5504252eb0 · < 524599714558da83747c04952d378155c69f5b6b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ipvs: fix reversed sequence option serialization
hton_seq() expects the host-order source first and the unaligned network-order destination second. The version 1 sync sender passes these arguments in reverse for both sequence blocks. This leaves 24 bytes of the kmalloc-backed message unwritten. It may disclose stale heap data and replace the live connection sequence state with values read from the buffer.
Pass the connection sequence state as the source and the message payload as the destination for both blocks.
From the CVE record · Linux
The Linux kernel's ipvs version 1 sync sender reverses arguments when serializing two sequence blocks, leaving 24 bytes of a message unwritten. Sync messages may disclose stale heap data and replace live connection sequence state with values from the buffer. The input does not specify attacker access or interaction requirements.
Engineers running Linux kernels that use the ipvs version 1 sync sender should check their versions; affected versions were not provided.