In the Linux kernel, the following vulnerability has been resolved:
vsock: fix buffer size clamping order
In vsockupdatebuffer_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->buffersize to grow beyond the configured vsk->buffermax_size.
Fix this by checking the minimum first, and then the maximum. This ensures the buffer size never exceeds the buffermaxsize.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46234.json",
"cna_assigner": "Linux"
}