CVE-2026-46273

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. a secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

June 3, 2026

Last Modified

August 7, 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.

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-14ubuntu
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (136 versions)7.0.7-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 49× 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 335 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 August 7, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 67.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46273?
CVE-2026-46273 has a CVSS v3 base score of 8.6 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs