CVE-2025-38457
MediumIn 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/[email protected]/
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
2.6.20
and later are affected. Fixed in
5.4.296,
5.10.240,
5.15.189,
6.1.146,
6.6.99,
6.12.39,
6.15.7,
6.16
and their respective stable series.
References
The following references provide additional information about CVE-2025-38457 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
Third Party Advisory
-
Third Party Advisory
-
-
PatchKernel patch commithttps://git.kernel.org/stable/c/23c165dde88eac405eebb59051ea1fe139a45803
-
PatchKernel patch commithttps://git.kernel.org/stable/c/25452638f133ac19d75af3f928327d8016952c8e
-
PatchKernel patch commithttps://git.kernel.org/stable/c/4c691d1b6b6dbd73f30ed9ee7da05f037b0c49af
Frequently asked questions
-
What is CVE-2025-38457?
CVE-2025-38457 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 2.6.20 onward and has been patched in 5.4.296, 5.10.240, 5.15.189 and others. CVE-2025-38457 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38457?
CVE-2025-38457 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2025-38457?
Yes — CVE-2025-38457 has been patched. Fixed versions include 5.4.296, 5.10.240, 5.15.189 and others. If you are running Linux kernel 2.6.20 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38457 actively exploited?
No — CVE-2025-38457 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.