BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49066High confidence

veth: Ensure eth header is in skb's linear part

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55138

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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

What

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

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49048 Référence CVE CVE-2022-49049 https://www.cve.org/CVERecord?id=CVE-2022-49049 Référence CVE CVE-2022-49052 https://www.cve.org/CVERecord?id=CVE-2022-49052 Référence CVE CVE-2022-49057 https://www.cve.org/CVERecord?id=CVE-2022-49057 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49061 https://www.cve.org/CVERecord?id=CVE-2022-49061 Référence CVE CVE-2022-49062 https://www.cve.org/CVERecord?id=CVE-2022-49062 Référence CVE CVE-2022-49064 https://www.cve.org/CVERecord?id=CVE-2022-49064 Référence CVE CVE-2022-49065 https://www.cve.org/CVERecord?id=CVE-2022-49065 Référence CVE CVE-2022-49066 https://www.cve.org/CVERecord?id=CVE-2022-49066 Référence CVE CVE-2022-49070 https://www.cve.org/CVERecord?id=CVE-2022-49070 Référence CVE CVE-2022-49072 https://www.cve.org/CVERecord?id=CVE-2022-49072 Référence CVE CVE-2022-49074 https://www.cve.org/CVERecord?id=CVE-2022-49074 Référence CVE CVE-2022-49077 https://www.cve.org/CVERecord?id=CVE-2022-49077 Référence CVE CVE-2022-49080 https://www.cve.org/CVERecord?id=CVE-2022-49080 Référence CVE CVE-2022-49086 https://www.cve.org/CVERecord?id=CVE-2022-49086 Référence CVE CVE-2022-49089 https://www.cve.org/CVERecord?id=CVE-2022-49089 Référence CVE CVE-2022-49090 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49057 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49059 https://www.cve.org/CVERecord?id=CVE-2022-49059 Référence CVE CVE-2022-49060 https://www.cve.org/CVERecord?id=CVE-2022-49060 Référence CVE CVE-2022-49061 https://www.cve.org/CVERecord?id=CVE-2022-49061 Référence CVE CVE-2022-49062 https://www.cve.org/CVERecord?id=CVE-2022-49062 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49064 https://www.cve.org/CVERecord?id=CVE-2022-49064 Référence CVE CVE-2022-49065 https://www.cve.org/CVERecord?id=CVE-2022-49065 Référence CVE CVE-2022-49066 https://www.cve.org/CVERecord?id=CVE-2022-49066 Référence CVE CVE-2022-49070 https://www.cve.org/CVERecord?id=CVE-2022-49070 Référence CVE CVE-2022-49071 https://www.cve.org/CVERecord?id=CVE-2022-49071 Référence CVE CVE-2022-49073 https://www.cve.org/CVERecord?id=CVE-2022-49073 Référence CVE CVE-2022-49074 https://www.cve.org/CVERecord?id=CVE-2022-49074 Référence CVE CVE-2022-49075 https://www.cve.org/CVERecord?id=CVE-2022-49075 Référence CVE CVE-2022-49076 https://www.cve.org/CVERecord?id=CVE-2022-49076 Référence CVE CVE-2022-49078 https://www.cve.org/CVERecord?id=CVE-2022-49078 Référence CVE CVE-2022-49082 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49057 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49059 https://www.cve.org/CVERecord?id=CVE-2022-49059 Référence CVE CVE-2022-49060 https://www.cve.org/CVERecord?id=CVE-2022-49060 Référence CVE CVE-2022-49061 https://www.cve.org/CVERecord?id=CVE-2022-49061 Référence CVE CVE-2022-49062 https://www.cve.org/CVERecord?id=CVE-2022-49062 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49064 https://www.cve.org/CVERecord?id=CVE-2022-49064 Référence CVE CVE-2022-49065 https://www.cve.org/CVERecord?id=CVE-2022-49065 Référence CVE CVE-2022-49066 https://www.cve.org/CVERecord?id=CVE-2022-49066 Référence CVE CVE-2022-49070 https://www.cve.org/CVERecord?id=CVE-2022-49070 Référence CVE CVE-2022-49071 https://www.cve.org/CVERecord?id=CVE-2022-49071 Référence CVE CVE-2022-49073 https://www.cve.org/CVERecord?id=CVE-2022-49073 Référence CVE CVE-2022-49074 https://www.cve.org/CVERecord?id=CVE-2022-49074 Référence CVE CVE-2022-49075 https://www.cve.org/CVERecord?id=CVE-2022-49075 Référence CVE CVE-2022-49076 https://www.cve.org/CVERecord?id=CVE-2022-49076 Référence CVE CVE-2022-49078 https://www.cve.org/CVERecord?id=CVE-2022-49078 Référence CVE CVE-2022-49082 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49051 Référence CVE CVE-2022-49054 https://www.cve.org/CVERecord?id=CVE-2022-49054 Référence CVE CVE-2022-49055 https://www.cve.org/CVERecord?id=CVE-2022-49055 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49059 https://www.cve.org/CVERecord?id=CVE-2022-49059 Référence CVE CVE-2022-49060 https://www.cve.org/CVERecord?id=CVE-2022-49060 Référence CVE CVE-2022-49061 https://www.cve.org/CVERecord?id=CVE-2022-49061 Référence CVE CVE-2022-49063 https://www.cve.org/CVERecord?id=CVE-2022-49063 Référence CVE CVE-2022-49065 https://www.cve.org/CVERecord?id=CVE-2022-49065 Référence CVE CVE-2022-49066 https://www.cve.org/CVERecord?id=CVE-2022-49066 Référence CVE CVE-2022-49073 https://www.cve.org/CVERecord?id=CVE-2022-49073 Référence CVE CVE-2022-49074 https://www.cve.org/CVERecord?id=CVE-2022-49074 Référence CVE CVE-2022-49076 https://www.cve.org/CVERecord?id=CVE-2022-49076 Référence CVE CVE-2022-49078 https://www.cve.org/CVERecord?id=CVE-2022-49078 Référence CVE CVE-2022-49082 https://www.cve.org/CVERecord?id=CVE-2022-49082 Référence CVE CVE-2022-49083 https://www.cve.org/CVERecord?id=CVE-2022-49083 Référence CVE CVE-2022-49084 https://www.cve.org/CVERecord?id=CVE-2022-49084 Référence CVE CVE-2022-49085 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 3de2a02b60a4ef0ab76263216f08c7d095fc7c42; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < d417a859221f127e8edf09c14b76ab50f825e171; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 1ef0088e43af1de4e3b365218c4d3179d9a37eec; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 2fd90b86dff413fbf8128780c04ea9c6849c16e2; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < d67c900f1947d64ba8a64f693504bcaab8d9000c; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 93940fc4cb81840dc0fa202de48cccb949a0261d; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 46bc359fec0c6d87b70d7a008bcd9a5e30dd6f27; e314dbdc1c0dc6a548ecf0afce28ecfd538ff568 < 726e2c5929de841fdcef4e2bf995680688ae1b87
Fixed
< 2.6.24; 4.9.311 ≤ 4.9.*; 4.14.276 ≤ 4.14.*; 4.19.239 ≤ 4.19.*; 5.4.190 ≤ 5.4.*; 5.10.112 ≤ 5.10.*; 5.15.35 ≤ 5.15.*; 5.17.4 ≤ 5.17.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 11 May 2026, 18:52 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55138
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-55138↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49066 · cve.blacktree.nl