Linux Kernel up to 6.12.62/6.17.12/6.18.1 /include/linux/skbuff.h __netif_receive_skb_core 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.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.62/6.17.12/6.18.1. It has been classified as critical. Impacted is the function __netif_receive_skb_core of the file /include/linux/skbuff.h. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2025-68363. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.62/6.17.12/6.18.1 and classified as critical. This issue affects the function __netif_receive_skb_core of the file /include/linux/skbuff.h. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: bpf: Check skb->transport_header is set in bpf_skb_check_mtu The bpf_skb_check_mtu helper needs to use skb->transport_header when the BPF_MTU_CHK_SEGS flag is used: bpf_skb_check_mtu(skb, ifindex, &mtu_len, 0, BPF_MTU_CHK_SEGS) The transport_header is not always set. There is a WARN_ON_ONCE report when CONFIG_DEBUG_NET is enabled + skb->gso_size is set + bpf_prog_test_run is used: WARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071 skb_gso_validate_network_len bpf_skb_check_mtu bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch bpf_test_run bpf_prog_test_run_skb For a normal ingress skb (not test_run), skb_reset_transport_header is performed but there is plan to avoid setting it as described in commit 2170a1f09148 ("net: no longer reset transport_header in __netif_receive_skb_core()"). This patch fixes the bpf helper by checking skb_transport_header_was_set(). The check is done just before skb->transport_header is used, to avoid breaking the existing bpf prog. The WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-68363 since 12/16/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/12/2026).

The vulnerability scanner Nessus provides a plugin with the ID 279712 (Linux Distros Unpatched Vulnerability : CVE-2025-68363), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.63, 6.17.13, 6.18.2 or 6.19-rc1 eliminates this vulnerability. Applying the patch 30ce906557a21adef4cba5901c8e995dc18263a9/1c30e4afc5507f0069cc09bd561e510e4d97fbf7/942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5/d946f3c98328171fa50ddb908593cf833587f725 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 (279712), EUVD (EUVD-2025-205091) and CERT Bund (WID-SEC-2025-2920). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Open Source Linux Kernel

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.3

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

CVSSv2info

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

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

Exploitinginfo

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

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 279712
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-68363

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.63/6.17.13/6.18.2/6.19-rc1
Patch: 30ce906557a21adef4cba5901c8e995dc18263a9/1c30e4afc5507f0069cc09bd561e510e4d97fbf7/942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5/d946f3c98328171fa50ddb908593cf833587f725

Timelineinfo

12/16/2025 CVE reserved
12/24/2025 +8 days Advisory disclosed
12/24/2025 +0 days VulDB entry created
01/12/2026 +19 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68363 (🔒)
GCVE (CVE): GCVE-0-2025-68363
GCVE (VulDB): GCVE-100-338189
EUVD: 🔒
CERT Bund: WID-SEC-2025-2920 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 15:25
Updated: 01/12/2026 05:30
Changes: 12/24/2025 15:25 (58), 12/25/2025 04:35 (2), 12/25/2025 19:18 (7), 01/12/2026 05:30 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!