CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment
Noroxi assessment
Priority: Plan (action score 40/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.49% (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 0c3024afabb8064b141f3cedcb1ddd6ab05ad9d5, 2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139, 3205b0652a37255dbb7ca8f3d942c8d8aa677c21; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to Linux Linux 0c3024afabb8064b141f3cedcb1ddd6ab05ad9d5, 2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139, 3205b0652a37255dbb7ca8f3d942c8d8aa677c21; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 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: veth: fix skb length accounting after XDP frag adjustment veth exposes non-linear skb fragments through an xdp_buff. If an XDP program adjusts the fragment area, veth_xdp_rcv_skb() copies xdp_frags_size back to skb->data_len but leaves skb->len containing the old fragment contribution. After a fragment shrink, this makes skb_headlen() larger than the actual linear area. In the reproduced UDP receive path, __skb_datagram_iter() copied 1024 bytes past the actual linear tail to userspace, starting at struct skb_shared_info. The copied bytes included the affected skb's nr_frags, xdp_frags_size, and a kernel pointer from skb_shinfo(skb)->frags[0]. Real packet data was displaced by the same amount and truncated at the end. Subtract the old data_len before replacing it and add the new data_len afterwards, keeping skb->len and skb->data_len synchronized. Additionally, bpf_xdp_pull_data() can advance data_end while leaving frags present. The skb is then still non-linear, so the old __skb_put(skb, off) triggers SKB_LINEAR_ASSERT(). Use skb_set_tail_pointer() and update skb->len explicitly instead, following bpf_prog_run_generic_xdp(). Unlike __skb_put(), skb_set_tail_pointer() does not require a linear skb. A 60000-byte UDP datagram on a veth pair with MTU 64000 was shortened by 1024 bytes from its fragment area. Before the fix, all 10 runs produced corrupted payloads. After the fix, all 10 runs matched the expected payload exactly. A forced-tailroom reproducer also exercises bpf_xdp_pull_data() with frags still present; the old code triggers SKB_LINEAR_ASSERT(), while this fix passes 10/10 runs.
- EUVD-2026-64549
- SUSE-SU-2026:23993-1
- SUSE-SU-2026:23994-1
- SUSE-SU-2026:23995-1
- SUSE-SU-2026:23996-1
- SUSE-SU-2026:23997-1
- SUSE-SU-2026:23998-1
- SUSE-SU-2026:23999-1
- SUSE-SU-2026:24000-1
- SUSE-SU-2026:24001-1
- SUSE-SU-2026:24002-1
- SUSE-SU-2026:24003-1
- SUSE-SU-2026:24004-1
- SUSE-SU-2026:24005-1
- SUSE-SU-2026:24006-1
- SUSE-SU-2026:24007-1
- SUSE-SU-2026:24008-1
- SUSE-SU-2026:24009-1
- SUSE-SU-2026:24010-1
- SUSE-SU-2026:24016-1
- Published
- Aug 22, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- —
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 10.0
- 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.
—
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
- 5.18affected
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before 0c3024afabb8064b141f3cedcb1ddd6ab05ad9d5affected · git
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before 2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139affected · git
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before 41b96667d42b74bb4b137f1bb78b611a953c5943affected · git
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before cdf745b7a777f87f51666e5d8f4c6fc279bcf54daffected · git
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before 3205b0652a37255dbb7ca8f3d942c8d8aa677c21affected · git
- 718a18a0c8a67f97781e40bdef7cdd055c430996 and later · before cb6379feaaff11c4e1e79c26c745ffa23182768aaffected · git
- before 5.18not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.152 and later · up to and including 6.6.*not affected · semver
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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_16 | before 15-150600.2.1 | 15-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_21 | before 10-150600.2.1 | 10-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_29 | before 4-150600.2.1 | 4-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_30 | before 3-150600.2.1 | 3-150600.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_18 | before 5-150700.2.1 | 5-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_19 | before 4-150700.2.1 | 4-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_20 | before 3-150700.2.1 | 3-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_21 | before 2-150700.2.1 | 2-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_4 | before 18-150700.2.1 | 18-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_7 | before 13-150700.2.1 | 13-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_13 | before 8-150700.2.1 | 8-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_19 | before 3-150700.2.1 | 3-150700.2.1 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_20 | before 2-150700.2.1 | 2-150700.2.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_11 | before 17-1.1 | 17-1.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_12 | before 17-1.1 | 17-1.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_13 | before 15-1.1 | 15-1.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_14 | before 13-1.2 | 13-1.2 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_16 | before 12-1.1 | 12-1.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_17 | before 11-1.1 | 11-1.1 |
| SUSE:Linux Micro 6.1 | kernel-livepatch-MICRO-6-0_Update_18 | before 10-1.1 | 10-1.1 |
+61
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74610Aug 22, 2026 · tls: don't leave a full plaintext sk_msg ring unpushed31Monitor
- ← EarlierCVE-2026-74611Aug 22, 2026 · tls: rx: restore msg_iter before TLS 1.3 optimistic retry39Monitor
- Later →CVE-2026-74613Aug 22, 2026 · vsock/virtio: avoid refilling the RX queue after teardown31Monitor
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 | 0c3024afabb8064b141f3cedcb1ddd6ab05ad9d5 | Vendor (CNA) |
| Linux Linux | 2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139 | Vendor (CNA) |
| Linux Linux | 3205b0652a37255dbb7ca8f3d942c8d8aa677c21 | Vendor (CNA) |
| Linux Linux | 41b96667d42b74bb4b137f1bb78b611a953c5943 | Vendor (CNA) |
| Linux Linux | cb6379feaaff11c4e1e79c26c745ffa23182768a | Vendor (CNA) |
| Linux Linux | cdf745b7a777f87f51666e5d8f4c6fc279bcf54d | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_16 | 15-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_21 | 10-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_29 | 4-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_18 | 5-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_19 | 4-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_20 | 3-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_21 | 2-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_4 | 18-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7_Update_7 | 13-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_13 | 8-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_19 | 3-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP7-RT_Update_20 | 2-150700.2.1 · SUSE:Linux Enterprise Live Patching 15 SP7 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_10 | 8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_11 | 8-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_12 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_13 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_14 | 6-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_15 | 4-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_16 | 3-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_5 | 12-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-livepatch-SLE16-RT_Update_6 | 11-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
+3
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2f2a7f3f8b9f1bffc9b0488aa02b6951b2aec139
- git.kernel.org/stable/c/3205b0652a37255dbb7ca8f3d942c8d8aa677c21
- git.kernel.org/stable/c/41b96667d42b74bb4b137f1bb78b611a953c5943
- git.kernel.org/stable/c/cb6379feaaff11c4e1e79c26c745ffa23182768a
- git.kernel.org/stable/c/cdf745b7a777f87f51666e5d8f4c6fc279bcf54d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.