CVE-2026-43194: net: consume xmit errors of GSO frames
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 0c9de092ef8c50a7ee9612811566f0aa81d8d7b6, 4cb163e9efcac4cd35c3043e097f25081a5c015c, 56bd32c0edca34041a5c215887fcf562fae2e2db.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0c9de092ef8c50a7ee9612811566f0aa81d8d7b6, 4cb163e9efcac4cd35c3043e097f25081a5c015c, 56bd32c0edca34041a5c215887fcf562fae2e2db or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net: consume xmit errors of GSO frames udpgro_frglist.sh and udpgro_bench.sh are the flakiest tests currently in NIPA. They fail in the same exact way, TCP GRO test stalls occasionally and the test gets killed after 10min. These tests use veth to simulate GRO. They attach a trivial ("return XDP_PASS;") XDP program to the veth to force TSO off and NAPI on. Digging into the failure mode we can see that the connection is completely stuck after a burst of drops. The sender's snd_nxt is at sequence number N [1], but the receiver claims to have received (rcv_nxt) up to N + 3 * MSS [2]. Last piece of the puzzle is that senders rtx queue is not empty (let's say the block in the rtx queue is at sequence number N - 4 * MSS [3]). In this state, sender sends a retransmission from the rtx queue with a single segment, and sequence numbers N-4*MSS:N-3*MSS [3]. Receiver sees it and responds with an ACK all the way up to N + 3 * MSS [2]. But sender will reject this ack as TCP_ACK_UNSENT_DATA because it has no recollection of ever sending data that far out [1]. And we are stuck. The root cause is the mess of the xmit return codes. veth returns an error when it can't xmit a frame. We end up with a loss event like this: ------------------------------------------------- | GSO super frame 1 | GSO super frame 2 | |-----------------------------------------------| | seg | seg | seg | seg | seg | seg | seg | seg | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | ------------------------------------------------- x ok ok <ok>| ok ok ok <x> \\ snd_nxt "x" means packet lost by veth, and "ok" means it went thru. Since veth has TSO disabled in this test it sees individual segments. Segment 1 is on the retransmit queue and will be resent. So why did the sender not advance snd_nxt even tho it clearly did send up to seg 8? tcp_write_xmit() interprets the return code from the core to mean that data has not been sent at all. Since TCP deals with GSO super frames, not individual segment the crux of the problem is that loss of a single segment can be interpreted as loss of all. TCP only sees the last return code for the last segment of the GSO frame (in <> brackets in the diagram above). Of course for the problem to occur we need a setup or a device without a Qdisc. Otherwise Qdisc layer disconnects the protocol layer from the device errors completely. We have multiple ways to fix this. 1) make veth not return an error when it lost a packet. While this is what I think we did in the past, the issue keeps reappearing and it's annoying to debug. The game of whack a mole is not great. 2) fix the damn return codes We only talk about NETDEV_TX_OK and NETDEV_TX_BUSY in the documentation, so maybe we should make the return code from ndo_start_xmit() a boolean. I like that the most, but perhaps some ancient, not-really-networking protocol would suffer. 3) make TCP ignore the errors It is not entirely clear to me what benefit TCP gets from interpreting the result of ip_queue_xmit()? Specifically once the connection is established and we're pushing data - packet loss is just packet loss? 4) this fix Ignore the rc in the Qdisc-less+GSO case, since it's unreliable. We already always return OK in the TCQ_F_CAN_BYPASS case. In the Qdisc-less case let's be a bit more conservative and only mask the GSO errors. This path is taken by non-IP-"networks" like CAN, MCTP etc, so we could regress some ancient thing. This is the simplest, but also maybe the hackiest fix? Similar fix has been proposed by Eric in the past but never committed because original reporter was working with an OOT driver and wasn't providing feedback (see Link).
- Published
- May 6, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-754
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.18affected
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before ae3f627b45fbc3c776a4e484696f3cad7cbb4ecaaffected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before 0c9de092ef8c50a7ee9612811566f0aa81d8d7b6affected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before 56bd32c0edca34041a5c215887fcf562fae2e2dbaffected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before 9ac6aebef4b4bfc5ed408b0b65645981574bc780affected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before ea5d7787635e26ec1194ec7eec0e8e5ae3bd10a5affected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before 4cb163e9efcac4cd35c3043e097f25081a5c015caffected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before c86901d22c89a6bf4e2f013e948aaabc60869893affected · git
- 1f59533f9ca5634e7b8914252e48aee9d9cbe501 and later · before 7aa767d0d3d04e50ae94e770db7db8197f666970affected · git
- before 3.18not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.18 and later · before 5.10.252
- linux linux kernel5.11 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
- linux linux kernel7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
| SUSE:Linux Micro 6.0 | kernel-default | before 6.4.0-50.1 | 6.4.0-50.1 |
| SUSE:Linux Micro 6.0 | kernel-kvmsmall | before 6.4.0-50.1 | 6.4.0-50.1 |
| SUSE:Linux Micro 6.0 | kernel-rt | before 6.4.0-50.1 | 6.4.0-50.1 |
| SUSE:Linux Micro 6.0 | kernel-source | before 6.4.0-50.2 | 6.4.0-50.2 |
| SUSE:Linux Micro 6.0 | kernel-source-rt | before 6.4.0-50.2 | 6.4.0-50.2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43192May 6, 2026 · dm mpath: Add missing dm_put_device when failing to get scsi dh name22Monitor
- ← EarlierCVE-2026-43193May 6, 2026 · nfsd: fix nfs4_file refcount leak in nfsd_get_dir_deleg()22Monitor
- Later →CVE-2026-43195May 6, 2026 · drm/amdgpu: validate user queue size constraints22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0c9de092ef8c50a7ee9612811566f0aa81d8d7b6 | Vendor (CNA) |
| Linux Linux | 4cb163e9efcac4cd35c3043e097f25081a5c015c | Vendor (CNA) |
| Linux Linux | 56bd32c0edca34041a5c215887fcf562fae2e2db | Vendor (CNA) |
| Linux Linux | 7aa767d0d3d04e50ae94e770db7db8197f666970 | Vendor (CNA) |
| Linux Linux | 9ac6aebef4b4bfc5ed408b0b65645981574bc780 | Vendor (CNA) |
| Linux Linux | ae3f627b45fbc3c776a4e484696f3cad7cbb4eca | Vendor (CNA) |
| Linux Linux | c86901d22c89a6bf4e2f013e948aaabc60869893 | Vendor (CNA) |
| Linux Linux | ea5d7787635e26ec1194ec7eec0e8e5ae3bd10a5 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-50.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.4.0-50.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-50.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-50.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-50.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39682243 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2026-3163712 days apartrxrpc: reject undecryptable rxkad response tickets39Monitor
- CVE-2026-431330 days apartKVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation31Monitor
- CVE-2026-3166612 days apartbtrfs: fix incorrect return value after changing leaf in lookup_extent_data_ref()31Monitor
- CVE-2026-6384374 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring31Monitor
- CVE-2026-6384774 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0196 · May 8, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4cb163e9efcac4cd35c3043e097f25081a5c015c
- git.kernel.org/stable/c/56bd32c0edca34041a5c215887fcf562fae2e2db
- git.kernel.org/stable/c/7aa767d0d3d04e50ae94e770db7db8197f666970
- git.kernel.org/stable/c/9ac6aebef4b4bfc5ed408b0b65645981574bc780
- git.kernel.org/stable/c/ae3f627b45fbc3c776a4e484696f3cad7cbb4eca
- git.kernel.org/stable/c/c86901d22c89a6bf4e2f013e948aaabc60869893
- git.kernel.org/stable/c/ea5d7787635e26ec1194ec7eec0e8e5ae3bd10a5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.