CVE-2025-38457
net/sched: Abort __tc_modify_qdisc if parent class does not exist
Reported by linux · Published July 25, 2025
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/
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-libbpf-devel | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| bpftool | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-modules-extra | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel6.12-libbpf-devel | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-tools | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel-livepatch-6.12.40-63.114 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| kernel6.12-modules-extra-common | Amazon Linux | 1:6.12.40-63.114.amzn2023 |
| kernel-devel | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.147-172.266.amzn2023 |
13 more packages have a fixed version. See every fix in Lookup.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6, 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6, 5e50da01d0ce7ef0ba3ed6cfabd62f327da0aca6 |
| Linux | Linux | 2.6.20, 0, 5.4.296 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | 3.1.5 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel6.12-libbpf-devel | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-livepatch-6.12.40-63.114 | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel | 0 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | 3.1.5 |
…and 15 more
Timeline
- Jul 25, 2025 CVE Published
- Jul 26, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (26 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (253 in total, the first dated here)
- Mar 29, 2026 Security Advisory (270 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
- Oct 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38457
vulnetix vdb fixes CVE-2025-38457
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38457/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart