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.

No CVSS v4.0

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00018.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
Linux Linux unaffected
Version Status Constraints
b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97 affected < a998a7e250bf976539e05a00ec64a81292afecaa
b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97 affected < 310da27932dd0afe7ce7456dfe1f0814c3301f41
b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97 affected < 2602f7bb5818e92315feeaeb71d8ce4d5c9ab160
b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97 affected < 0b68881501460c3761f196469e1e503218c5e536
b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97 affected < d114bfdc9b76bf93b881e195b7ec957c14227bab
Linux Linux affected
Version Status Constraints
5.5 affected —
0 unaffected < 5.5
6.6.140 unaffected ≤ 6.6.*
6.12.90 unaffected ≤ 6.12.*
6.18.32 unaffected ≤ 6.18.*
7.0.9 unaffected ≤ 7.0.*
7.1-rc1 unaffected ≤ *

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

No data.

Project Subscriptions

Vendors Products
Linux Subscribe
Linux Kernel Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536 cve-icon cve-icon
https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160 cve-icon cve-icon
https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41 cve-icon cve-icon
https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaa cve-icon cve-icon
https://git.kernel.org/stable/c/d114bfdc9b76bf93b881e195b7ec957c14227bab cve-icon cve-icon
History

Thu, 28 May 2026 12:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Thu, 28 May 2026 10:15:00 +0000

Type Values Removed Values Added
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.
Title vsock: fix buffer size clamping order
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-28T09:40:58.373Z

Reserved: 2026-05-13T15:03:33.106Z

Link: CVE-2026-46234

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-05-28T10:16:39.043

Modified: 2026-05-28T13:44:01.663

Link: CVE-2026-46234

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-28T12:30:16Z

Weaknesses