CVE-2026-46234: vsock: fix buffer size clamping order
In the Linux kernel, the following vulnerability has been resolved:
vsock: fix buffer size clamping order
In vsockupdatebuffersize(), 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->buffermaxsize.
Fix this by checking the minimum first, and then the maximum. This ensures the buffer size never exceeds the buffermaxsize.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.141.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46234?
The severity of CVE-2026-46234 is classified as risk 27.
How do I fix CVE-2026-46234?
To fix CVE-2026-46234, update the Linux kernel to the latest patched version that addresses this vulnerability.
Who is affected by CVE-2026-46234?
CVE-2026-46234 affects systems running the Linux kernel that utilize vsock functionality.
What are the implications of CVE-2026-46234?
CVE-2026-46234 can potentially allow improper buffer handling due to the incorrect clamping order.
When was CVE-2026-46234 published?
CVE-2026-46234 was published on May 28, 2026.