Linux Kernel up to 6.12.62/6.17.12/6.18.1 sch_cake cake_drop null pointer dereference

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.5$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 rated as critical. This impacts the function cake_drop of the component sch_cake. The manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2025-68325. There is no exploit available. Upgrading the affected component is advised.

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 cake_drop of the component sch_cake. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop In cake_drop(), qdisc_tree_reduce_backlog() is used to update the qlen and backlog of the qdisc hierarchy. Its caller, cake_enqueue(), assumes that the parent qdisc will enqueue the current packet. However, this assumption breaks when cake_enqueue() returns NET_XMIT_CN: the parent qdisc stops enqueuing current packet, leaving the tree qlen/backlog accounting inconsistent. This mismatch can lead to a NULL dereference (e.g., when the parent Qdisc is qfq_qdisc). This patch computes the qlen/backlog delta in a more robust way by observing the difference before and after the series of cake_drop() calls, and then compensates the qdisc tree accounting if cake_enqueue() returns NET_XMIT_CN. To ensure correct compensation when ACK thinning is enabled, a new variable is introduced to keep qlen unchanged.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2025-68325 since 12/16/2025. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 279256 (Linux Distros Unpatched Vulnerability : CVE-2025-68325), 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 0b6216f9b3d1c33c76f74511026e5de5385ee520/529c284cc2815c8350860e9a31722050fe7117cb/3ed6c458530a547ed0c9ea0b02b19bab620be88b/9fefc78f7f02d71810776fdeb119a05a946a27cc 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 (279256), EUVD (EUVD-2025-204267) and CERT Bund (WID-SEC-2025-2904). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

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.7
VulDB Meta Temp Score: 5.5

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

CVSSv2info

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

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

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
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: 279256
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-68325

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: 0b6216f9b3d1c33c76f74511026e5de5385ee520/529c284cc2815c8350860e9a31722050fe7117cb/3ed6c458530a547ed0c9ea0b02b19bab620be88b/9fefc78f7f02d71810776fdeb119a05a946a27cc

Timelineinfo

12/16/2025 CVE reserved
12/18/2025 +2 days Advisory disclosed
12/18/2025 +0 days VulDB entry created
01/12/2026 +25 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-68325 (🔒)
GCVE (CVE): GCVE-0-2025-68325
GCVE (VulDB): GCVE-100-337379
EUVD: 🔒
CERT Bund: WID-SEC-2025-2904 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 12/18/2025 17:17
Updated: 01/12/2026 05:59
Changes: 12/18/2025 17:17 (59), 12/19/2025 17:03 (2), 12/20/2025 01:00 (7), 01/12/2026 05:59 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!