CVE-2026-46234

NVD 0.07.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
Trending — 4 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
EG Score
7.8(low)
EPSS
2.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (8)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f6ec135941d2c1c2dbb87b5ce1783f4f6ac6ccca
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d114bfdc9b76bf93b881e195b7ec957c14227bab
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/caf11dfea5233a69298a1c448bbf8d1639c80536
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a998a7e250bf976539e05a00ec64a81292afecaa
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/310da27932dd0afe7ce7456dfe1f0814c3301f41
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2602f7bb5818e92315feeaeb71d8ce4d5c9ab160
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b68881501460c3761f196469e1e503218c5e536
generic

vsock: fix buffer size clamping order - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01ef69785dc3162f588a361ab770b1e312800188

Vendor Advisories for CVE-2026-46234(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 142 total refreshes for this CVE.

  1. 2026-07-16 10:17 UTCEG score recompute
  2. 2026-07-16 10:17 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 20:30 UTCEG score recompute
  9. 2026-07-11 20:30 UTCVendor advisory
  10. 2026-07-11 20:30 UTCGHSA enrichment
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 18:12 UTCEG score recompute
  14. 2026-07-08 18:12 UTCVendor advisory
  15. 2026-07-08 18:12 UTCGHSA enrichment
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-02 14:11 UTCEG score recompute
  22. 2026-07-02 14:11 UTCVendor advisory
  23. 2026-07-02 14:11 UTCGHSA enrichment
  24. 2026-07-01 15:30 UTCEG score recompute
  25. 2026-07-01 15:30 UTCVendor advisory
Show 75 more
  1. 2026-07-01 15:30 UTCGHSA enrichment
  2. 2026-07-01 03:04 UTCEG score recompute
  3. 2026-07-01 03:04 UTCVendor advisory
  4. 2026-07-01 03:04 UTCGHSA enrichment
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 02:00 UTCEG score recompute
  7. 2026-06-30 02:00 UTCVendor advisory
  8. 2026-06-30 02:00 UTCGHSA enrichment
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 13:43 UTCEG score recompute
  12. 2026-06-29 13:43 UTCVendor advisory
  13. 2026-06-29 13:43 UTCGHSA enrichment
  14. 2026-06-28 19:00 UTCEG score recompute
  15. 2026-06-28 19:00 UTCVendor advisory
  16. 2026-06-28 19:00 UTCGHSA enrichment
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 06:37 UTCEG score recompute
  19. 2026-06-28 06:37 UTCVendor advisory
  20. 2026-06-28 06:37 UTCGHSA enrichment
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 18:11 UTCEG score recompute
  24. 2026-06-27 18:11 UTCVendor advisory
  25. 2026-06-27 18:11 UTCGHSA enrichment
  26. 2026-06-27 05:26 UTCEG score recompute
  27. 2026-06-27 05:26 UTCVendor advisory
  28. 2026-06-27 05:26 UTCGHSA enrichment
  29. 2026-06-27 03:08 UTCEPSS rescore
  30. 2026-06-26 16:49 UTCEG score recompute
  31. 2026-06-26 16:49 UTCVendor advisory
  32. 2026-06-26 16:49 UTCGHSA enrichment
  33. 2026-06-25 20:36 UTCEG score recompute
  34. 2026-06-25 20:36 UTCVendor advisory
  35. 2026-06-25 20:36 UTCGHSA enrichment
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-25 08:16 UTCEG score recompute
  38. 2026-06-25 08:16 UTCVendor advisory
  39. 2026-06-25 08:16 UTCGHSA enrichment
  40. 2026-06-24 16:51 UTCEG score recompute
  41. 2026-06-24 16:51 UTCVendor advisory
  42. 2026-06-24 16:51 UTCGHSA enrichment
  43. 2026-06-24 14:05 UTCEPSS rescore
  44. 2026-06-23 21:33 UTCEPSS rescore
  45. 2026-06-23 21:33 UTCEPSS rescore
  46. 2026-06-22 14:25 UTCEPSS rescore
  47. 2026-06-22 14:25 UTCEPSS rescore
  48. 2026-06-21 14:56 UTCEPSS rescore
  49. 2026-06-21 14:56 UTCEPSS rescore
  50. 2026-06-21 01:59 UTCEPSS rescore
  51. 2026-06-21 01:59 UTCEPSS rescore
  52. 2026-06-19 19:26 UTCEPSS rescore
  53. 2026-06-19 19:26 UTCEPSS rescore
  54. 2026-06-18 17:52 UTCEPSS rescore
  55. 2026-06-18 17:52 UTCEPSS rescore
  56. 2026-06-17 18:12 UTCEG score recompute
  57. 2026-06-17 18:12 UTCGHSA enrichment
  58. 2026-06-17 17:53 UTCEPSS rescore
  59. 2026-06-17 03:58 UTCEG score recompute
  60. 2026-06-17 03:58 UTCGHSA enrichment
  61. 2026-06-16 17:52 UTCEPSS rescore
  62. 2026-06-16 15:41 UTCEG score recompute
  63. 2026-06-16 15:41 UTCVendor advisory
  64. 2026-06-16 15:41 UTCGHSA enrichment
  65. 2026-06-16 01:14 UTCEG score recompute
  66. 2026-06-16 01:14 UTCVendor advisory
  67. 2026-06-16 01:14 UTCGHSA enrichment
  68. 2026-06-15 17:49 UTCEPSS rescore
  69. 2026-06-15 12:56 UTCEG score recompute
  70. 2026-06-15 12:56 UTCVendor advisory
  71. 2026-06-15 12:56 UTCGHSA enrichment
  72. 2026-06-14 23:33 UTCMITRE cvelistV5
  73. 2026-06-14 21:08 UTCEG score recompute
  74. 2026-06-14 21:08 UTCVendor advisory
  75. 2026-06-14 21:08 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2026-46234?
CVE-2026-46234 is a publicly disclosed vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock: fix buffer size clamping order In vsockupdatebuffer_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…
When was CVE-2026-46234 disclosed?
CVE-2026-46234 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46234 actively exploited?
CVE-2026-46234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46234, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46234

Explore →

Is Your Infrastructure Affected by CVE-2026-46234?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.