All reports
Medium

kernel: vsock: fix buffer size clamping order

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-46234

Probability of exploitation in the next 30 days: 0.13%

FIRST EPSS · 2026-11-20

Description

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.

A flaw was found in the Linux kernel's vsock component. This vulnerability stems from an incorrect order in which buffer sizes are validated, allowing a local user to set a minimum buffer size larger than the maximum. This can cause the socket's memory to exceed its defined boundaries, potentially leading to resource exhaustion or system instability, which could result in a Denial of Service (DoS).