CVE-2025-38457

net/sched: Abort __tc_modify_qdisc if parent class does not exist

State
Published
Severity
Not scored
Published
Jul 25, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

net/sched: Abort __tc_modify_qdisc if parent class does not exist

Lion's patch [1] revealed an ancient bug in the qdisc API. Whenever a user creates/modifies a qdisc specifying as a parent another qdisc, the qdisc API will, during grafting, detect that the user is not trying to attach to a class and reject. However grafting is performed after qdisc_create (and thus the qdiscs' init callback) is executed. In qdiscs that eventually call qdisc_tree_reduce_backlog during init or change (such as fq, hhf, choke, etc), an issue arises. For example, executing the following commands:

sudo tc qdisc add dev lo root handle a: htb default 2 sudo tc qdisc add dev lo parent a: handle beef fq

Qdiscs such as fq, hhf, choke, etc unconditionally invoke qdisc_tree_reduce_backlog() in their control path init() or change() which then causes a failure to find the child class; however, that does not stop the unconditional invocation of the assumed child qdisc's qlen_notify with a null class. All these qdiscs make the assumption that class is non-null.

The solution is ensure that qdisc_leaf() which looks up the parent class, and is invoked prior to qdisc_create(), should return failure on not finding the class. In this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the parentid doesn't correspond to a class, so that we can detect it earlier on and abort before qdisc_create is called.

[1] https://lore.kernel.org/netdev/d912cbd7-193b-4269-9857-525bee8bbb6a@gmail.com/

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 923a276c74e25073ae391e930792ac86a9f77f1eAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 90436e72c9622c2f70389070088325a3232d339fAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 25452638f133ac19d75af3f928327d8016952c8eAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 23c165dde88eac405eebb59051ea1fe139a45803Affected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 4c691d1b6b6dbd73f30ed9ee7da05f037b0c49afAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before 8ecd651ef24ab50123692a4e3e25db93cb11602aAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before e28a383d6485c3bb51dc5953552f76c4dea33eeaAffected
  • 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 to before ffdde7bf5a439aaa1955ebd581f5c64ab1533963Affected
LinuxLinux
  • 2.6.20Affected
  • before 2.6.20Not affected
  • 5.4.296 through 5.4.*Not affected
  • 5.10.240 through 5.10.*Not affected
  • 5.15.189 through 5.15.*Not affected
  • 6.1.146 through 6.1.*Not affected
  • 6.6.99 through 6.6.*Not affected
  • 6.12.39 through 6.12.*Not affected
  • 6.15.7 through 6.15.*Not affected
  • 6.16 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.