High · published May 28, 2026
In the Linux kernel, the following vulnerability has been resolved:
vsock: fix buffer size clamping order
In vsock_update_buffer_size(), the buffer size was being clamped to the
maximum first, and then to the minimum. If a user sets a minimum buffer
size larger than the maximum, the minimum check overrides the maximum
check, inverting the constraint.
This breaks the intended socket memory boundaries by allowing the
vsk->buffer_size to grow beyond the configured vsk->buffer_max_size.
Fix this by checking the minimum first, and then the maximum. This
ensures the buffer size never exceeds the buffer_max_size.
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 5.5, < 5.10.258 | 5.10.258 |
| linux/linux_kernel | ≥ 5.11, < 5.15.209 | 5.15.209 |
| linux/linux_kernel | ≥ 5.16, < 6.1.175 | 6.1.175 |
| linux/linux_kernel | ≥ 6.2, < 6.6.140 | 6.6.140 |
| linux/linux_kernel | ≥ 6.7, < 6.12.90 | 6.12.90 |
| linux/linux_kernel | ≥ 6.13, < 6.18.32 | 6.18.32 |
| linux/linux_kernel | ≥ 6.19, < 7.0.9 | 7.0.9 |