---
id: CVE-2026-46234
title: |-
  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
summary: |-
  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 …
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-787
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.5, < 5.10.258'
  - 'linux_kernel >= 5.11, < 5.15.209'
  - 'linux_kernel >= 5.16, < 6.1.175'
  - 'linux_kernel >= 6.2, < 6.6.140'
  - 'linux_kernel >= 6.7, < 6.12.90'
  - 'linux_kernel >= 6.13, < 6.18.32'
  - 'linux_kernel >= 6.19, < 7.0.9'
patched:
  - linux_kernel 7.0.9
published: '2026-05-28'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:19:50.947'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-46234'
references:
  - url: 'https://git.kernel.org/stable/c/01ef69785dc3162f588a361ab770b1e312800188'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/caf11dfea5233a69298a1c448bbf8d1639c80536'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d114bfdc9b76bf93b881e195b7ec957c14227bab'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-784472.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00176
epssPercentile: 0.06633
ingestedAt: '2026-10-15T03:30:12.897Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 5.5, < 5.10.258`
- `linux_kernel >= 5.11, < 5.15.209`
- `linux_kernel >= 5.16, < 6.1.175`
- `linux_kernel >= 6.2, < 6.6.140`
- `linux_kernel >= 6.7, < 6.12.90`
- `linux_kernel >= 6.13, < 6.18.32`
- `linux_kernel >= 6.19, < 7.0.9`

## Remediation

Upgrade past the affected range:

- `linux_kernel 7.0.9`