CVE-2025-39677: net/sched: Fix backlog accounting in qdisc_dequeue_internal
In the Linux kernel, the following vulnerability has been resolved:
net/sched: Fix backlog accounting in qdisc_dequeue_internal
This issue applies for the following qdiscs: hhf, fq, fq_codel, and
fq_pie, and occurs in their change handlers when adjusting to the new
limit. The problem is the following in the values passed to the
subsequent qdisc_tree_reduce_backlog call given a tbf parent:
When the tbf parent runs out of tokens, skbs of these qdiscs will
be placed in gso_skb. Their peek handlers are qdisc_peek_dequeued,
which accounts for both qlen and backlog. However, in the case of
qdisc_dequeue_internal, ONLY qlen is accounted for when pulling
from gso_skb. This means that these qdiscs are missing a
qdisc_qstats_backlog_dec when dropping packets to satisfy the
new limit in their change handlers.
One can observe this issue with the following (with tc patched to
support a limit of 0):
export TARGET=fq
tc qdisc del dev lo root
tc qdisc add dev lo root handle 1: tbf rate 8bit burst 100b latency 1ms
tc qdisc replace dev lo handle 3: parent 1:1 $TARGET limit 1000
echo ''; echo 'add child'; tc -s -d qdisc show dev lo
ping -I lo -f -c2 -s32 -W0.001 127.0.0.1 2>&1 >/dev/null
echo ''; echo 'after ping'; tc -s -d qdisc show dev lo
tc qdisc change dev lo handle 3: parent 1:1 $TARGET limit 0
echo ''; echo 'after limit drop'; tc -s -d qdisc show dev lo
tc qdisc replace dev lo handle 2: parent 1:1 sfq
echo ''; echo 'post graft'; tc -s -d qdisc show dev lo
The second to last show command shows 0 packets but a positive
number (74) of backlog bytes. The problem becomes clearer in the
last show command, where qdisc_purge_queue triggers
qdisc_tree_reduce_backlog with the positive backlog and causes an
underflow in the tbf parent's backlog (4096 Mb instead of 0).
To fix this issue, the codepath for all clients of qdisc_dequeue_internal
has been simplified: codel, pie, hhf, fq, fq_pie, and fq_codel.
qdisc_dequeue_internal handles the backlog adjustments for all cases that
do not directly use the dequeue handler.
The old fq_codel_change limit adjustment loop accumulated the arguments to
the subsequent qdisc_tree_reduce_backlog call through the cstats field.
However, this is confusing and error prone as fq_codel_dequeue could also
potentially mutate this field (which qdisc_dequeue_internal calls in the
non gso_skb case), so we have unified the code here with other qdiscs.
Security readout for executives and security teams
Plain-English summary
A Linux traffic-shaping accounting flaw can leave incorrect backlog values and eventually underflow parent queue statistics. It requires a particular TBF and child-queue configuration plus a limit change. The supplied sources demonstrate corrupted accounting but do not explain how the rated confidentiality, integrity, and availability impacts arise in practice.
Executive priority
Treat this as a high-priority kernel maintenance issue on traffic-shaping infrastructure using the affected configuration. Other Linux systems should be inventoried, but the sources do not justify emergency organization-wide response or claims of active exploitation.
Technical view
When TBF exhausts tokens, packets may enter gso_skb. qdisc_dequeue_internal reduced queue length without reducing backlog bytes, leaving stale accounting when hhf, fq, fq_codel, or fq_pie limits changed. Later queue purging could underflow the TBF parent's backlog. The correction centralizes backlog adjustment for affected dequeue clients.
Likely exposure
Exposure is most likely on Linux systems using a TBF parent with hhf, fq, fq_codel, or fq_pie child disciplines whose limits can be changed. The supplied version data marks Linux affected but does not provide sufficiently clear range semantics for reliable package-level conclusions.
Exploitation context
CVSS 3.1 rates this 7.8 with local access, low complexity, low privileges, and no user interaction. The bundle marks KEV false, and no supplied source reports active exploitation. Evidence shows reproducible accounting corruption; it does not establish a public weaponized exploit or concrete compromise path.
Researcher notes
The observable symptom is zero queued packets with positive backlog bytes, followed by parent-backlog underflow during queue replacement or purging. The fix also simplifies accounting paths for codel and pie clients. Exact affected release boundaries and the mechanism supporting CVSS's high confidentiality and integrity impacts remain unclear from the supplied material.
Mitigation direction
Update to a distribution-supported kernel containing the referenced stable correction.
Check the Linux distribution's advisory for exact fixed packages and reboot requirements.
If patching is delayed, follow vendor guidance; the supplied sources name no separate supported workaround.
Prioritize remediation on hosts using the identified TBF and child-qdisc combination.
Validation and detection
Record each host's running kernel version and distribution package release.
Inspect traffic-control configurations for TBF parents with hhf, fq, fq_codel, or fq_pie children.
Confirm the installed kernel contains a referenced correction or a documented vendor backport.
After updating and rebooting, verify the fixed kernel is actually running.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-39677 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.