CVE-2025-39766: net/sched: Make cake_enqueue return NET_XMIT_CN when past buffer_limit
In the Linux kernel, the following vulnerability has been resolved:
net/sched: Make cakeenqueue return NETXMITCN when past bufferlimit
The following setup can trigger a WARNING in htbactivate due to the condition: !cl->leaf.q->q.qlen
tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 \ htb rate 64bit tc qdisc add dev lo parent 1:1 handle f: \ cake memlimit 1b ping -I lo -f -c1 -s64 -W0.001 127.0.0.1
This is because the low memlimit leads to a low bufferlimit, which causes packet dropping. However, cakeenqueue still returns NETXMITSUCCESS, causing htbenqueue to call htbactivate with an empty child qdisc. We should return NETXMITCN when packets are dropped from the same tin and flow.
I do not believe return value of NETXMITCN is necessary for packet drops in the case of ack filtering, as that is meant to optimize performance, not to signal congestion.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39766?
The severity of CVE-2025-39766 has not been officially rated, but it may lead to issues in network scheduling operations under specific conditions.
How do I fix CVE-2025-39766?
To fix CVE-2025-39766, it is recommended to update to the latest version of the Linux kernel where the vulnerability has been resolved.
What systems are affected by CVE-2025-39766?
CVE-2025-39766 affects systems running vulnerable versions of the Linux kernel.
What is the impact of CVE-2025-39766?
The impact of CVE-2025-39766 includes potential warnings in the htb_activate function during network queue management.
Is there a workaround for CVE-2025-39766?
Currently, there are no specific workarounds for CVE-2025-39766, so updating the kernel to secure versions is the best approach.