Linux
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
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < e5bee633cc276410337d54b99f77fbc1ad8801e5
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 6672e6c00810056acaac019fe26cdc26fee8a66c
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < a0ec22fa20b252edbe070a9de8501eef63c17ef5
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 295f7c579b07b5b7cf2dffe485f71cc2f27647cb
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 2f2190ce4ca972051cac6a8d7937448f8cb9673c
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 4e38eaaabfb7fffbb371a51150203e19eee5d70e
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < 39ed887b1dd2d6b720f87e86692ac3006cc111c8
- >= 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea, < ac9fe7dd8e730a103ae4481147395cc73492d786
Fixed in e5bee633cc276410337d54b99f77fbc1ad8801e5, 6672e6c00810056acaac019fe26cdc26fee8a66c, 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28, a0ec22fa20b252edbe070a9de8501eef63c17ef5, 295f7c579b07b5b7cf2dffe485f71cc2f27647cb, 2f2190ce4ca972051cac6a8d7937448f8cb9673c, 4e38eaaabfb7fffbb371a51150203e19eee5d70e, 39ed887b1dd2d6b720f87e86692ac3006cc111c8, ac9fe7dd8e730a103ae4481147395cc73492d786
- 5.0
Fixed in 0, 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.32, 6.14.10, 6.15.1, 6.16
Mitigation
Upgrade Linux to e5bee633cc276410337d54b99f77fbc1ad8801e5 or 6672e6c00810056acaac019fe26cdc26fee8a66c or 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28 or a0ec22fa20b252edbe070a9de8501eef63c17ef5 or 295f7c579b07b5b7cf2dffe485f71cc2f27647cb or 2f2190ce4ca972051cac6a8d7937448f8cb9673c or 4e38eaaabfb7fffbb371a51150203e19eee5d70e or 39ed887b1dd2d6b720f87e86692ac3006cc111c8 or ac9fe7dd8e730a103ae4481147395cc73492d786 or later.
Upgrade Linux to 0 or 5.4.294 or 5.10.238 or 5.15.185 or 6.1.141 or 6.6.93 or 6.12.32 or 6.14.10 or 6.15.1 or 6.16 or later.
Timeline
Days relative to CVE publicationFirst public PoC 35 days after publication; not in CISA KEV. First PoC: 0xdevil/CVE-2025-38001 (created 11 Jul 2025, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs · 1 informational
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0xdevil/CVE-2025-38001 | 11 Jul 2025 +35 d | 90 | PoC |
| khoatran107/cve-2025-38001 | 25 Aug 2025 +80 d | 1 | PoC |
| Jevil36239/CVE-2025-38001 | 10 May 2026 +338 d | 0 | PoC |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| ngobao2002/CVE-2025-38001-test | 10 Oct 2025 +126 d | 0 | Informational · write-up |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.