Linux Kernel up to 6.1.1 bpf include/linux/skbuff.h __dev_queue_xmit privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.1.1. It has been classified as problematic. This impacts the function __dev_queue_xmit in the library include/linux/skbuff.h of the component bpf. Performing a manipulation results in an unknown weakness. This vulnerability is reported as CVE-2022-50253. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 6.1.1. This affects the function __dev_queue_xmit in the library include/linux/skbuff.h of the component bpf. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: bpf: make sure skb->len != 0 when redirecting to a tunneling device syzkaller managed to trigger another case where skb->len == 0 when we enter __dev_queue_xmit: WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 skb_assert_len include/linux/skbuff.h:2576 [inline] WARNING: CPU: 0 PID: 2470 at include/linux/skbuff.h:2576 __dev_queue_xmit+0x2069/0x35e0 net/core/dev.c:4295 Call Trace: dev_queue_xmit+0x17/0x20 net/core/dev.c:4406 __bpf_tx_skb net/core/filter.c:2115 [inline] __bpf_redirect_no_mac net/core/filter.c:2140 [inline] __bpf_redirect+0x5fb/0xda0 net/core/filter.c:2163 ____bpf_clone_redirect net/core/filter.c:2447 [inline] bpf_clone_redirect+0x247/0x390 net/core/filter.c:2419 bpf_prog_48159a89cb4a9a16+0x59/0x5e bpf_dispatcher_nop_func include/linux/bpf.h:897 [inline] __bpf_prog_run include/linux/filter.h:596 [inline] bpf_prog_run include/linux/filter.h:603 [inline] bpf_test_run+0x46c/0x890 net/bpf/test_run.c:402 bpf_prog_test_run_skb+0xbdc/0x14c0 net/bpf/test_run.c:1170 bpf_prog_test_run+0x345/0x3c0 kernel/bpf/syscall.c:3648 __sys_bpf+0x43a/0x6c0 kernel/bpf/syscall.c:5005 __do_sys_bpf kernel/bpf/syscall.c:5091 [inline] __se_sys_bpf kernel/bpf/syscall.c:5089 [inline] __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5089 do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48 entry_SYSCALL_64_after_hwframe+0x61/0xc6 The reproducer doesn't really reproduce outside of syzkaller environment, so I'm taking a guess here. It looks like we do generate correct ETH_HLEN-sized packet, but we redirect the packet to the tunneling device. Before we do so, we __skb_pull l2 header and arrive again at skb->len == 0. Doesn't seem like we can do anything better than having an explicit check after __skb_pull?

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50253 since 09/15/2025. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/10/2026).

The vulnerability scanner Nessus provides a plugin with the ID 279063 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:4422-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16 or 6.1.2 eliminates this vulnerability. Applying the patch ffbccc5fb0a67424e12f7f8da210c04c8063f797/e6a63203e5a90a39392fa1a7ffc60f5e9baf642a/772431f30ca040cfbf31b791d468bac6a9ca74d3/6d935a02658be82585ecb39aab339faa84496650/5d3f4478d22b2cb1810f6fe0f797411e9d87b3e5/1b65704b8c08ae92db29f720d3b298031131da53/f186303845a01cc7e991f9dc51d7e5a3cdc7aedb/07ec7b502800ba9f7b8b15cb01dd6556bb41aaca is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (279063) and CERT Bund (WID-SEC-2025-2053). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • F5 F5OS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279063
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2025:4422-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.303/4.19.270/5.4.229/5.10.163/5.15.86/6.0.16/6.1.2
Patch: ffbccc5fb0a67424e12f7f8da210c04c8063f797/e6a63203e5a90a39392fa1a7ffc60f5e9baf642a/772431f30ca040cfbf31b791d468bac6a9ca74d3/6d935a02658be82585ecb39aab339faa84496650/5d3f4478d22b2cb1810f6fe0f797411e9d87b3e5/1b65704b8c08ae92db29f720d3b298031131da53/f186303845a01cc7e991f9dc51d7e5a3cdc7aedb/07ec7b502800ba9f7b8b15cb01dd6556bb41aaca

Timelineinfo

09/15/2025 Advisory disclosed
09/15/2025 +0 days CVE reserved
09/15/2025 +0 days VulDB entry created
01/10/2026 +117 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50253 (🔒)
GCVE (CVE): GCVE-0-2022-50253
GCVE (VulDB): GCVE-100-323937
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/15/2025 16:40
Updated: 01/10/2026 09:03
Changes: 09/15/2025 16:40 (58), 09/16/2025 17:25 (7), 11/27/2025 03:38 (10), 12/19/2025 03:01 (2), 12/28/2025 05:50 (1), 01/10/2026 09:03 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to stay up to date on a daily basis?

Enable the mail alert feature now!