veth: Ensure eth header is in skb's linear part
Noroxi assessment
Priority: Monitor (action score 22/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.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1ef0088e43af1de4e3b365218c4d3179d9a37eec, 2fd90b86dff413fbf8128780c04ea9c6849c16e2, 3de2a02b60a4ef0ab76263216f08c7d095fc7c42.
Low priority for now. Upgrade to Linux Linux 1ef0088e43af1de4e3b365218c4d3179d9a37eec, 2fd90b86dff413fbf8128780c04ea9c6849c16e2, 3de2a02b60a4ef0ab76263216f08c7d095fc7c42 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: Ensure eth header is in skb's linear part After feeding a decapsulated packet to a veth device with act_mirred, skb_headlen() may be 0. But veth_xmit() calls __dev_forward_skb(), which expects at least ETH_HLEN byte of linear data (as __dev_forward_skb2() calls eth_type_trans(), which pulls ETH_HLEN bytes unconditionally). Use pskb_may_pull() to ensure veth_xmit() respects this constraint. kernel BUG at include/linux/skbuff.h:2328! RIP: 0010:eth_type_trans+0xcf/0x140 Call Trace: <IRQ> __dev_forward_skb2+0xe3/0x160 veth_xmit+0x6e/0x250 [veth] dev_hard_start_xmit+0xc7/0x200 __dev_queue_xmit+0x47f/0x520 ? skb_ensure_writable+0x85/0xa0 ? skb_mpls_pop+0x98/0x1c0 tcf_mirred_act+0x442/0x47e [act_mirred] tcf_action_exec+0x86/0x140 fl_classify+0x1d8/0x1e0 [cls_flower] ? dma_pte_clear_level+0x129/0x1a0 ? dma_pte_clear_level+0x129/0x1a0 ? prb_fill_curr_block+0x2f/0xc0 ? skb_copy_bits+0x11a/0x220 __tcf_classify+0x58/0x110 tcf_classify_ingress+0x6b/0x140 __netif_receive_skb_core.constprop.0+0x47d/0xfd0 ? __iommu_dma_unmap_swiotlb+0x44/0x90 __netif_receive_skb_one_core+0x3d/0xa0 netif_receive_skb+0x116/0x170 be_process_rx+0x22f/0x330 [be2net] be_poll+0x13c/0x370 [be2net] __napi_poll+0x2a/0x170 net_rx_action+0x22f/0x2f0 __do_softirq+0xca/0x2a8 __irq_exit_rcu+0xc1/0xe0 common_interrupt+0x83/0xa0
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.24 and later · before 4.9.311
- linux linux kernel4.10 and later · before 4.14.276
- linux linux kernel4.15 and later · before 4.19.239
- linux linux kernel4.20 and later · before 5.4.190
- linux linux kernel5.5 and later · before 5.10.112
- linux linux kernel5.11 and later · before 5.15.35
- linux linux kernel5.16 and later · before 5.17.4
- linux linux kernel5.18
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
- 2.6.24affected
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 3de2a02b60a4ef0ab76263216f08c7d095fc7c42affected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before d417a859221f127e8edf09c14b76ab50f825e171affected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 1ef0088e43af1de4e3b365218c4d3179d9a37eecaffected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 2fd90b86dff413fbf8128780c04ea9c6849c16e2affected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before d67c900f1947d64ba8a64f693504bcaab8d9000caffected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 93940fc4cb81840dc0fa202de48cccb949a0261daffected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 46bc359fec0c6d87b70d7a008bcd9a5e30dd6f27affected · git
- e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 and later · before 726e2c5929de841fdcef4e2bf995680688ae1b87affected · git
- before 2.6.24not 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 5.17.6-1 | 5.17.6-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.255.1 | 4.12.14-122.255.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_67 | before 1-8.5.1 | 1-8.5.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.255.1 | 4.12.14-122.255.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.255.1 | 4.12.14-122.255.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49064Feb 26, 2025 · cachefiles: unmark inode in use in error path22Monitor
- ← EarlierCVE-2022-49065Feb 26, 2025 · SUNRPC: Fix the svc_deferred_event trace class22Monitor
- Later →CVE-2022-49067Feb 26, 2025 · powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit22Monitor
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 | 1ef0088e43af1de4e3b365218c4d3179d9a37eec | Vendor (CNA) |
| Linux Linux | 2fd90b86dff413fbf8128780c04ea9c6849c16e2 | Vendor (CNA) |
| Linux Linux | 3de2a02b60a4ef0ab76263216f08c7d095fc7c42 | Vendor (CNA) |
| Linux Linux | 46bc359fec0c6d87b70d7a008bcd9a5e30dd6f27 | Vendor (CNA) |
| Linux Linux | 726e2c5929de841fdcef4e2bf995680688ae1b87 | Vendor (CNA) |
| Linux Linux | 93940fc4cb81840dc0fa202de48cccb949a0261d | Vendor (CNA) |
| Linux Linux | d417a859221f127e8edf09c14b76ab50f825e171 | Vendor (CNA) |
| Linux Linux | d67c900f1947d64ba8a64f693504bcaab8d9000c | Vendor (CNA) |
| debian:linux | 5.17.6-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.255.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.255.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.255.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_67 | 1-8.5.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | 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.
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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2fd90b86dff413fbf8128780c04ea9c6849c16e2
- git.kernel.org/stable/c/3de2a02b60a4ef0ab76263216f08c7d095fc7c42
- git.kernel.org/stable/c/46bc359fec0c6d87b70d7a008bcd9a5e30dd6f27
- git.kernel.org/stable/c/726e2c5929de841fdcef4e2bf995680688ae1b87
- git.kernel.org/stable/c/93940fc4cb81840dc0fa202de48cccb949a0261d
- git.kernel.org/stable/c/d417a859221f127e8edf09c14b76ab50f825e171
- git.kernel.org/stable/c/d67c900f1947d64ba8a64f693504bcaab8d9000c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.