CVE-2026-46234 Details
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 vulnerability in the Linux kernel's virtual socket (vsock) implementation has been addressed. The issue arose in the buffer size management within the vsock_update_buffer_size() function. The vulnerability allowed the buffer size to exceed the maximum limit by improperly prioritizing minimum size checks over maximum ones. This flaw could enable the buffer size to grow beyond the designated maximum, disrupting intended memory boundaries. The vulnerability affects the Linux kernel stable tree.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for upgrading the Linux kernel can be found in the official Linux documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/01ef69785dc3162f588a361ab770b1e312800188 | kernel.org | Patch |
| https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536 | kernel.org | Patch |
| https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160 | kernel.org | Patch |
| https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaa | kernel.org | Patch |
| https://git.kernel.org/stable/c/caf11dfea5233a69298a1c448bbf8d1639c80536 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d114bfdc9b76bf93b881e195b7ec957c14227bab | kernel.org | Patch |
| https://git.kernel.org/stable/c/f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.5, < 5.10.258 >= 5.11, < 5.15.209 >= 5.16, < 6.1.175 >= 6.2, < 6.6.140 >= 6.7, < 6.12.90 >= 6.13, < 6.18.32 >= 6.19, < 7.0.9 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 10, 2026 | Initial Analysis | [email protected] |
| Jun 1, 2026 | CVE Modified | kernel.org |
| May 28, 2026 | New CVE Received | kernel.org |