CVE-2026-46273 — ibmveth: Disable GSO for packets with small MSS
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 <f10b09ef687f> ("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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.7% (30-day exploitation probability)+8
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < 86fc64584811d43c9ccd74447de58620189d8b77version 4.2≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < cc427d24ac6442ffdeafd157a63c7c5b73ed4de4≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < 3af24f0c4c31f18a4a2d927990759194832bb6e9≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < c1f261863e65b508f37416dfbc5c5d911c9b9233≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < db8012c631cb845e9ae2b4b531e17d86c9519755≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < 82bc89fbb82d9396fb4eaee8720ea85e2e787957≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < 1cdf5dbcec988d06f5f720bdf89e91073f77fa10 and 1 more≥ 8641dd85799f85bef5f0d1f87356aaa12cb2195e and < 9a5e984d7af910e46dcbed3ce77873e000a4f77d |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 4.2 and < 5.10.258version 7.1-rc1≥ 6.19 and < 7.0.7≥ 6.13 and < 6.18.30≥ 6.7 and < 6.12.88≥ 6.2 and < 6.6.140≥ 5.16 and < 6.1.175≥ 5.11 and < 5.15.209 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.6 | CVSS 3.1 | High | 3.9 | 4.0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.6 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.72%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 8.6
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/db8012c631cb845e9ae2b4b531e17d86c9519755
- git.kernel.org/stable/c/3af24f0c4c31f18a4a2d927990759194832bb6e9
- git.kernel.org/stable/c/1cdf5dbcec988d06f5f720bdf89e91073f77fa10
- git.kernel.org/stable/c/cc427d24ac6442ffdeafd157a63c7c5b73ed4de4
- git.kernel.org/stable/c/9a5e984d7af910e46dcbed3ce77873e000a4f77d
- git.kernel.org/stable/c/c1f261863e65b508f37416dfbc5c5d911c9b9233
- git.kernel.org/stable/c/86fc64584811d43c9ccd74447de58620189d8b77
- git.kernel.org/stable/c/82bc89fbb82d9396fb4eaee8720ea85e2e787957
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-46273 is "ibmveth: Disable GSO for packets with small MSS", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.6 describes technical severity. EPSS 0.72% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.