CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice
Noroxi assessment
Priority: Monitor (action score 22/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 295f7c579b07b5b7cf2dffe485f71cc2f27647cb, 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28, 2f2190ce4ca972051cac6a8d7937448f8cb9673c.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 295f7c579b07b5b7cf2dffe485f71cc2f27647cb, 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28, 2f2190ce4ca972051cac6a8d7937448f8cb9673c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- BDU:2025-12349
- DSA-5973-1
- RHSA-2025:12209
- RHSA-2025:12311
- RHSA-2025:14511
- RHSA-2025:14692
- RHSA-2025:14742
- RHSA-2025:14744
- RHSA-2025:15035
- RHSA-2025:16538
- RHSA-2025:16539
- RHSA-2025:16540
- RHSA-2025:16541
- RHSA-2025:16580
- RHSA-2025:16582
- RHSA-2025:16583
- SUSE-SU-2025:03097-1
- SUSE-SU-2025:03100-1
- SUSE-SU-2025:03104-1
- SUSE-SU-2025:03106-1
- Published
- Jun 6, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- CWE-835
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.0affected
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before e5bee633cc276410337d54b99f77fbc1ad8801e5affected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 6672e6c00810056acaac019fe26cdc26fee8a66caffected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28affected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before a0ec22fa20b252edbe070a9de8501eef63c17ef5affected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 295f7c579b07b5b7cf2dffe485f71cc2f27647cbaffected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 2f2190ce4ca972051cac6a8d7937448f8cb9673caffected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 4e38eaaabfb7fffbb371a51150203e19eee5d70eaffected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before 39ed887b1dd2d6b720f87e86692ac3006cc111c8affected · git
- 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and later · before ac9fe7dd8e730a103ae4481147395cc73492d786affected · git
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- debian debian linux12.0
- linux linux kernel5.11 and later · before 5.15.185
- linux linux kernel5.16 and later · before 6.1.141
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernel5.0.1 and later · before 5.4.294
- linux linux kernel6.13 and later · before 6.14.10
- linux linux kernel6.15 and later · before 6.15.1
- linux linux kernel6.7 and later · before 6.12.32
- linux linux kernel5.5 and later · before 5.10.238
- linux linux kernel5.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.32-1 | 6.12.32-1 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_16_1 | before 0:1-10.el8_10 | 0:1-10.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_16_1-debuginfo | before 0:1-10.el8_10 | 0:1-10.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_16_1-debugsource | before 0:1-10.el8_10 | 0:1-10.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_30_1 | before 0:1-9.el8_10 | 0:1-9.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_30_1-debuginfo | before 0:1-9.el8_10 | 0:1-9.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_30_1-debugsource | before 0:1-9.el8_10 | 0:1-9.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_40_1 | before 0:1-7.el8_10 | 0:1-7.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_40_1-debuginfo | before 0:1-7.el8_10 | 0:1-7.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_40_1-debugsource | before 0:1-7.el8_10 | 0:1-7.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_53_1 | before 0:1-5.el8_10 | 0:1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_53_1-debuginfo | before 0:1-5.el8_10 | 0:1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_53_1-debugsource | before 0:1-5.el8_10 | 0:1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_72_1 | before 0:1-2.el8_10 | 0:1-2.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_72_1-debuginfo | before 0:1-2.el8_10 | 0:1-2.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kpatch-patch-4_18_0-553_72_1-debugsource | before 0:1-2.el8_10 | 0:1-2.el8_10 |
| Red Hat:enterprise_linux:9::baseos | kpatch-patch-5_14_0-570_17_1 | before 0:1-10.el9_6 | 0:1-10.el9_6 |
| Red Hat:enterprise_linux:9::baseos | kpatch-patch-5_14_0-570_17_1-debuginfo | before 0:1-10.el9_6 | 0:1-10.el9_6 |
| Red Hat:enterprise_linux:9::baseos | kpatch-patch-5_14_0-570_17_1-debugsource | before 0:1-10.el9_6 | 0:1-10.el9_6 |
| Red Hat:rhel_aus:8.2::baseos | bpftool | before 0:4.18.0-193.165.1.el8_2 | 0:4.18.0-193.165.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | bpftool-debuginfo | before 0:4.18.0-193.165.1.el8_2 | 0:4.18.0-193.165.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel | before 0:4.18.0-193.165.1.el8_2 | 0:4.18.0-193.165.1.el8_2 |
| Red Hat:rhel_aus:8.2::baseos | kernel-abi-whitelists | before 0:4.18.0-193.165.1.el8_2 | 0:4.18.0-193.165.1.el8_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38002Jun 6, 2025 · io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo()22Monitor
- ← EarlierCVE-2025-38000Jun 6, 2025 · sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue()31Monitor
- Later →CVE-2025-38003Jun 8, 2025 · can: bcm: add missing rcu read protection for procfs content22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 295f7c579b07b5b7cf2dffe485f71cc2f27647cb | Vendor (CNA) |
| Linux Linux | 2c928b3a0b04a431ffcd6c8b7d88a267124a3a28 | Vendor (CNA) |
| Linux Linux | 2f2190ce4ca972051cac6a8d7937448f8cb9673c | Vendor (CNA) |
| Linux Linux | 39ed887b1dd2d6b720f87e86692ac3006cc111c8 | Vendor (CNA) |
| Linux Linux | 4e38eaaabfb7fffbb371a51150203e19eee5d70e | Vendor (CNA) |
| Linux Linux | 6672e6c00810056acaac019fe26cdc26fee8a66c | Vendor (CNA) |
| Linux Linux | a0ec22fa20b252edbe070a9de8501eef63c17ef5 | Vendor (CNA) |
| Linux Linux | ac9fe7dd8e730a103ae4481147395cc73492d786 | Vendor (CNA) |
| Linux Linux | e5bee633cc276410337d54b99f77fbc1ad8801e5 | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.128.1.el9_2 · Red Hat:rhel_e4s:9.2::appstream | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_49 | 15-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_51 | 11-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_54 | 7-150300.2.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_0 | 21-150600.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_1 | 20-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_10 | 5-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_11 | 4-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_5 | 14-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
+4
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×4
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 4 repositories | 2025-07-11 → 2026-05-10 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+34 d
- TodayNov 16, 2026+528 d
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31448320 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-63889408 days apartscsi: scsi_transport_fc: Widen FPIN pname walker counter to u3232Monitor
- CVE-2026-52933383 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()31Monitor
- CVE-2026-23451301 days apartbonding: prevent potential infinite loop in bond_header_parse()30Monitor
- CVE-2026-31552322 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
- CVE-2026-46052355 days apartceph: only d_add() negative dentries when they are unhashed30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- git.kernel.org/stable/c/2c928b3a0b04a431ffcd6c8b7d88a267124a3a28
- git.kernel.org/stable/c/2f2190ce4ca972051cac6a8d7937448f8cb9673c
- git.kernel.org/stable/c/39ed887b1dd2d6b720f87e86692ac3006cc111c8
- git.kernel.org/stable/c/4e38eaaabfb7fffbb371a51150203e19eee5d70e
- git.kernel.org/stable/c/6672e6c00810056acaac019fe26cdc26fee8a66c
- git.kernel.org/stable/c/a0ec22fa20b252edbe070a9de8501eef63c17ef5
- git.kernel.org/stable/c/ac9fe7dd8e730a103ae4481147395cc73492d786
- git.kernel.org/stable/c/e5bee633cc276410337d54b99f77fbc1ad8801e5
- syst3mfailure.io/rbtree-family-drama/
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.