CVE-2026-46273

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. the CNA's CVSS baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: 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:

ibmveth: Disable GSO for packets with small MSS

Some physical adapters on Power systems do not support segmentation offload when the MSS is less than 224 bytes. Attempting to send such packets causes the adapter to freeze, stopping all traffic until manually reset.

Implement ndo_features_check to disable GSO for packets with small MSS values. The network stack will perform software segmentation instead.

The 224-byte minimum matches ibmvnic commit ("ibmvnic: Enforce stronger sanity checks on GSO packets") which uses the same physical adapters in SEA configurations.

The issue occurs specifically when the hardware attempts to perform segmentation (gso_segs > 1) with a small MSS. Single-segment GSO packets (gso_segs == 1) do not trigger the problematic LSO code path and are transmitted normally without segmentation.

Add an ndo_features_check callback to disable GSO when MSS < 224 bytes. Also call vlan_features_check() to ensure proper handling of VLAN packets, particularly QinQ (802.1ad) configurations where the hardware parser may not support certain offload features.

Validated using iptables to force small MSS values. Without the fix, the adapter freezes. With the fix, packets are segmented in software and transmission succeeds. Comprehensive regression testing completedd (MSS tests, performance, stability).

CVSS v3
8.6
EG Score
8.6(medium)
EPSS
30.9%
KEV
Not listed

Published

June 3, 2026

Last Modified

June 14, 2026

Advisory Details (8)

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

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

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

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

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

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

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

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a5e984d7af910e46dcbed3ce77873e000a4f77d
generic

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86fc64584811d43c9ccd74447de58620189d8b77
generic

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82bc89fbb82d9396fb4eaee8720ea85e2e787957
generic

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3af24f0c4c31f18a4a2d927990759194832bb6e9
generic

ibmveth: Disable GSO for packets with small MSS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1cdf5dbcec988d06f5f720bdf89e91073f77fa10

Vendor Advisories for CVE-2026-46273(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 167× 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 181 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46273?
CVE-2026-46273 is a high vulnerability published on June 3, 2026. In the Linux kernel, the following vulnerability has been resolved: ibmveth: Disable GSO for packets with small MSS Some physical adapters on Power systems do not support segmentation offload when the MSS is less than 224 bytes. Attempting to send such packets causes the adapter to freeze, stopping…
When was CVE-2026-46273 disclosed?
CVE-2026-46273 was first published in the National Vulnerability Database on June 3, 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-46273 actively exploited?
CVE-2026-46273 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46273?
CVE-2026-46273 has a CVSS v4.0 base score of 8.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46273?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46273, 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-46273

Explore →

Is Your Infrastructure Affected by CVE-2026-46273?

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