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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.13%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 7.8 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.13% probability · 3th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-787
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/01ef69785dc3162f588a361ab770b1e312800188Patch
- https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536Patch
- https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160Patch
- https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41Patch
- https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaaPatch
- https://git.kernel.org/stable/c/caf11dfea5233a69298a1c448bbf8d1639c80536Patch
- https://git.kernel.org/stable/c/d114bfdc9b76bf93b881e195b7ec957c14227babPatch
- https://git.kernel.org/stable/c/f6ec135941d2c1c2dbb87b5ce1783f4f6ac6cccaPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.