# CVE-2026-46234: vsock: fix buffer size clamping order

> A logic error in Linux kernel vsock buffer size clamping allows memory boundaries to be bypassed, potentially leading to resource exhaustion or instability.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-89058, BELL-CVE-2026-46234, DEBIAN-CVE-2026-46234, GHSA-jc98-98jj-62cp, ROOT-OS-DEBIAN-11-CVE-2026-46234, ROOT-OS-DEBIAN-12-CVE-2026-46234, ROOT-OS-UBUNTU-2204-CVE-2026-46234, ROOT-OS-UBUNTU-2404-CVE-2026-46234, UBUNTU-CVE-2026-46234

## What is CVE-2026-46234?

CVE-2026-46234 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-46234?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46234?

Apply the vendor's patch.

## Is CVE-2026-46234 being exploited?

There is no known exploitation of CVE-2026-46234 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46234 and fix it if it is affected.

What it is: CVE-2026-46234 is a high-severity vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46234 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46234/ (Markdown: https://insights.sbomify.com/CVE-2026-46234/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46234
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46234
- OSV: https://osv.dev/vulnerability/CVE-2026-46234

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46234/
Summaries are generated and may contain mistakes; the official description above is the record.