🛡️ CVE-2025-38457 — debian-linux

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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/[email protected]/

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2025-38457 is recorded against 3 packages.

  • debian-linux
  • kernel (from 6.13.0 up to 6.15.7)
  • linux-kernel

Timeline and source

Published on 25 July 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
git.kernel.org
lists.debian.org
lists.debian.org
cert-portal.siemens.com

CVE-2025-38457 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity MEDIUM
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-07-25
Updated 2026-08-20
Modified 2026-06-17

Affected Packages

Software From version Fixed in
debian-linux
kernel 6.13.0 6.15.7
linux-kernel

References

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in debian-linux

CVE-2025-38457 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2025