🛡️ CVE-2025-38001 — debian-linux

🟠 CVSS 7.8 — High ✅ No Known Exploit CWE-835 NVD
7.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

net_sched: hfsc: Address reentrant enqueue adding class to eltree twice

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

net_sched: hfsc: Address reentrant enqueue adding class to eltree twice

Savino says:

"We are writing to report that this recent patch

(141d34391abbb315d68556b7c67ad97885407547) [1]

can be bypassed, and a UAF can still occur when HFSC is utilized with

NETEM.

The patch only checks the cl->cl_nactive field to determine whether

it is the first insertion or not [2], but this field is only

incremented by init_vf [3].

By using HFSC_RSC (which uses init_ed) [4], it is possible to bypass the

check and insert the class twice in the eltree.

Under normal conditions, this would lead to an infinite loop in

hfsc_dequeue for the reasons we already explained in this report [5].

However, if TBF is added as root qdisc and it is configured with a

very low rate,

it can be utilized to prevent packets from being dequeued.

This behavior can be exploited to perform subsequent insertions in the

HFSC eltree and cause a UAF."

To fix both the UAF and the infinite loop, with netem as an hfsc child,

check explicitly in hfsc_enqueue whether the class is already in the eltree

whenever the HFSC_RSC flag is set.

[1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=141d34391abbb315d68556b7c67ad97885407547

[2] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1572

[3] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L677

[4] https://elixir.bootlin.com/linux/v6.15-rc5/source/net/sched/sch_hfsc.c#L1574

[5] https://lore.kernel.org/netdev/8DuRWwfqjoRDLDmBMlIfbrsZg9Gx50DHJc1ilxsEBNe2D6NMoigR_eIRIG0LOjMc3r10nUUZtArXx4oZBIdUfZQrwjcQhdinnMis_0G7VEk=@willsroot.io/T/#u

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 high, integrity high, availability high.

Weakness class

CVE-2025-38001 is classified as CWE-835: Infinite Loop. A loop condition can never become false for some inputs, hanging the process.

Affected software

CVE-2025-38001 is recorded against 3 packages.

  • debian-linux
  • kernel (from 6.15.0 up to 6.15.1)
  • linux-kernel

Timeline and source

Published on 6 June 2025 and last revised on 30 July 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
git.kernel.org
syst3mfailure.io
lists.debian.org
lists.debian.org
syst3mfailure.io

CVE-2025-38001 on other distributions

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

Details

Severity HIGH
CVSS Score 7.8
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE CWE-835
Public Exploit ✅ No
Source NVD
Published 2025-06-06
Updated 2026-08-12
Modified 2026-07-30

Affected Packages

Software From version Fixed in
debian-linux
kernel 6.15.0 6.15.1
linux-kernel

References

Similar Threats

Site Security Check

Is debian-linux part of your stack?

CVE-2025-38001 is rated CVSS 7.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

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.