CVE-2026-46234

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.

CVSS 3.1

7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

0.1% chance of exploitation in the next 30 days; higher than 2% of CVEs (scores of 2026-10-25)

CWE

CWE-787

Published

2026-05-28

Modified

2026-10-15

Record from

the NVD, synced 2026-10-19

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/01ef69785dc3162f588a361ab770b1e312800188
• https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536
• https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160
• https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41
• https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaa

Check your stackJSON