VulnerabilityPublished 28 May 2026Updated 6 Nov 2026

CVE-2026-46234: Linux kernel · vsock: fix buffer size clamping order

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca, d114bfdc9b76bf93b881e195b7ec957c14227bab, caf11dfea5233a69298a1c448bbf8d1639c80536 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca	Fixed in f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < d114bfdc9b76bf93b881e195b7ec957c14227bab	Fixed in d114bfdc9b76bf93b881e195b7ec957c14227bab
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < caf11dfea5233a69298a1c448bbf8d1639c80536	Fixed in caf11dfea5233a69298a1c448bbf8d1639c80536
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < a998a7e250bf976539e05a00ec64a81292afecaa	Fixed in a998a7e250bf976539e05a00ec64a81292afecaa
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < 2602f7bb5818e92315feeaeb71d8ce4d5c9ab160	Fixed in 2602f7bb5818e92315feeaeb71d8ce4d5c9ab160
LinuxLinux	Affected ≥ b9f2b0ffde0c9b666b2b1672eb468b8f805a9b97, < 310da27932dd0afe7ce7456dfe1f0814c3301f41	Fixed in 310da27932dd0afe7ce7456dfe1f0814c3301f41

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.

References

Community reviews

Loading reviews…