CVE-2025-38001 | 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

Published: 2025-06-06 Last update: 2026-06-17 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Conclusion & alert: CVE-2025-38001 is rated Low Risk (32/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.36%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-38001

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.36% +0.35%
2 2025-12-18 0.09% 0.01% -0.09%
3 2025-11-18 0.09%

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-38001

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-38001

OS Trackers for CVE-2025-38001

vendor priority summary link
debian not yet assigned CVE-2025-38001 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 6. https://security-tracker.debian.org/tracker/CVE-2025-38001
redhat high https://access.redhat.com/security/cve/CVE-2025-38001
suse high https://www.suse.com/security/cve/CVE-2025-38001/
ubuntu medium CVE-2025-38001 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 204, ignored 147, not-affected 52, needs-triage 2, needed 1. https://ubuntu.com/security/CVE-2025-38001

Affected software / configurations for CVE-2025-38001

Vendor Product Version Raw CPE
linux linux_kernel >= 5.0.1, < 5.4.294 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.5, < 5.10.238 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.185 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.141 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.93 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.32 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.14.10 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.15, < 6.15.1 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:-:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc3:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc4:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc5:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc6:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc7:*:*:*:*:*:*
linux linux_kernel 5.0 cpe:2.3:o:linux:linux_kernel:5.0:rc8:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
debian debian_linux 12.0 cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*

References for CVE-2025-38001

URL Tags
https://git.kernel.org/stable/c/295f7c579b07b5b7cf2dffe485f71cc2f27647cb Patch
https://git.kernel.org/stable/c/2c928b3a0b04a431ffcd6c8b7d88a267124a3a28 Patch
https://git.kernel.org/stable/c/2f2190ce4ca972051cac6a8d7937448f8cb9673c Patch
https://git.kernel.org/stable/c/39ed887b1dd2d6b720f87e86692ac3006cc111c8 Patch
https://git.kernel.org/stable/c/4e38eaaabfb7fffbb371a51150203e19eee5d70e Patch
https://git.kernel.org/stable/c/6672e6c00810056acaac019fe26cdc26fee8a66c Patch
https://git.kernel.org/stable/c/a0ec22fa20b252edbe070a9de8501eef63c17ef5 Patch
https://git.kernel.org/stable/c/ac9fe7dd8e730a103ae4481147395cc73492d786 Patch
https://git.kernel.org/stable/c/e5bee633cc276410337d54b99f77fbc1ad8801e5 Patch
https://syst3mfailure.io/rbtree-family-drama/ Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html Third Party Advisory
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html Third Party Advisory
cvelogic Threat Intelligence