CVE-2026-90063 — virtio-net: Ensure that TCP packets don't overflow gso_segs
In the Linux kernel, the following vulnerability has been resolved: virtio-net: Ensure that TCP packets don't overflow gso_segs The user can specify any gso_size in a packet crafted with an AF_PACKET PACKET_VNET_HDR socket, even smaller than TCP_MIN_GSO_SIZE = 8. At the same time, GSO_MAX_SIZE = 8 * GSO_MAX_SEGS = 8 * 65535. When the user crafts a packet with gso_size < 8, there is a risk for partial GSO to overflow the 16-bit gso_segs field when dividing the SKB length by gso_size. Adjust gso_size of TCP packets to be at least TCP_MIN_GSO_SIZE = 8. Keep gso_size of UDP GSO packets, as gso_size=1 is valid and explicitly tested at tools/testing/selftests/net/tun.c:649.
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.2% (30-day exploitation probability)+2
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.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < d3d111fe809773edbb4ae121e36253b7d683509a≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < 8f6667a081887c2b59c6f3dd86c1789ada563762≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < 339f47ae04dcc6b5a730dd6bc70dddc8937c3260≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < 29bd12c7c5f9d6cf855b87bace18f71e9607f9e8≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < 0e5ed3b98d1d8d251acfdccfeaa607453ad12954≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < 75c271c48f483af678e514734e10b2452410e08c≥ 7c6d2ecbda83150b2036a2b36b21381ad4667762 and < c27c449d455aafd9018a3cbab150f1c42c87923fversion bfbaf151efe491e30697e21c8b7ae1b615480873 and 8 moreversion 6c83456601e65a6dd371ddf595510183d198e9b1version b3ebd9830c6026c98f03f7047c9d608573773f13version b96fb681ca789629b8ba3da99ca3b2e6fa807f0a≥ 4.14.187 and < 4.15≥ 4.19.131 and < 4.20≥ 5.4.46 and < 5.5≥ 5.6.18 and < 5.7version 5.7 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 19, 2026 · 4 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/75c271c48f483af678e514734e10b2452410e08c
- github.com/advisories/GHSA-86wj-v2pm-25hq
- nvd.nist.gov/vuln/detail/CVE-2026-90063
- git.kernel.org/stable/c/0e5ed3b98d1d8d251acfdccfeaa607453ad12954
- git.kernel.org/stable/c/8f6667a081887c2b59c6f3dd86c1789ada563762
- git.kernel.org/stable/c/c27c449d455aafd9018a3cbab150f1c42c87923f
- git.kernel.org/stable/c/339f47ae04dcc6b5a730dd6bc70dddc8937c3260
- git.kernel.org/stable/c/29bd12c7c5f9d6cf855b87bace18f71e9607f9e8
- git.kernel.org/stable/c/d3d111fe809773edbb4ae121e36253b7d683509a
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 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 CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- 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-90063 is "virtio-net: Ensure that TCP packets don't overflow gso_segs", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% 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.