FlawAtlas
Search the atlas
CVE-2025-38177 Not scored

sch_hfsc: make hfsc_qlen_notify() idempotent

In the Linux kernel, the following vulnerability has been resolved: sch_hfsc: make hfsc_qlen_notify() idempotent hfsc_qlen_notify() is not idempotent either and not friendly to its callers, like fq_codel_dequeue(). Let's make it idempotent to ease qdisc_tree_reduce_backlog() callers' life: 1. update_vf() decreases cl->cl_nactive, so we can check whether it is non-zero before calling it. 2. eltree_remove() always removes RB node cl->el_node, but we can use RB_EMPTY_NODE() + RB_CLEAR_NODE() to make it safe.

Exploit probability 0.2%
Published July 4, 2025
Required by Not available
Last source change July 15, 2026

02 / AFFECTED SOFTWARE

Affected packages

Linux Kernel
Unknown Unknown

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2025:20081-1
related SUSE-SU-2025:02846-1
related SUSE-SU-2025:02848-1
related SUSE-SU-2025:02849-1
related SUSE-SU-2025:02850-1
related SUSE-SU-2025:02851-1
related SUSE-SU-2025:02852-1
related SUSE-SU-2025:02853-1
related SUSE-SU-2025:02923-1
related SUSE-SU-2025:02969-1
related SUSE-SU-2025:02996-1
related SUSE-SU-2025:02997-1
related SUSE-SU-2025:03011-1
related SUSE-SU-2025:03023-1
related SUSE-SU-2025:03315-1
related SUSE-SU-2025:03317-1
related SUSE-SU-2025:03319-1
related SUSE-SU-2025:03329-1
related SUSE-SU-2025:03336-1
related SUSE-SU-2025:03337-1
related SUSE-SU-2025:03341-1
related SUSE-SU-2025:03342-1
related SUSE-SU-2025:03343-1
related SUSE-SU-2025:03344-1
related SUSE-SU-2025:03350-1
related SUSE-SU-2025:03358-1
related SUSE-SU-2025:03359-1
related SUSE-SU-2025:03362-1
related SUSE-SU-2025:03370-1
related SUSE-SU-2025:03374-1
related SUSE-SU-2025:03375-1
related SUSE-SU-2025:03381-1
related SUSE-SU-2025:03387-1
related SUSE-SU-2025:03391-1
related SUSE-SU-2025:03393-1
related SUSE-SU-2025:03395-1
related SUSE-SU-2025:03397-1
related SUSE-SU-2025:03400-1
related SUSE-SU-2025:03406-1
related SUSE-SU-2025:03408-1
related SUSE-SU-2025:03410-1
related SUSE-SU-2025:03414-1
related SUSE-SU-2025:03418-1
related SUSE-SU-2025:20577-1
related SUSE-SU-2025:20586-1
related SUSE-SU-2025:20601-1
related SUSE-SU-2025:20602-1
related SUSE-SU-2025:20722-1
related SUSE-SU-2025:20723-1
related SUSE-SU-2025:20724-1
related SUSE-SU-2025:20725-1
related SUSE-SU-2025:20726-1
related SUSE-SU-2025:20727-1
related SUSE-SU-2025:20728-1
related SUSE-SU-2025:20729-1
related SUSE-SU-2025:20730-1
related SUSE-SU-2025:20733-1
related SUSE-SU-2025:20734-1
related SUSE-SU-2025:20737-1
related SUSE-SU-2025:20738-1
related SUSE-SU-2025:20768-1
related SUSE-SU-2025:20769-1
related SUSE-SU-2025:20770-1
related SUSE-SU-2025:20771-1
related SUSE-SU-2025:20774-1
related SUSE-SU-2025:20784-1
related SUSE-SU-2025:20785-1
related SUSE-SU-2025:20786-1
related SUSE-SU-2025:20787-1
related SUSE-SU-2025:20788-1
related SUSE-SU-2025:20789-1
related SUSE-SU-2025:21074-1
related SUSE-SU-2025:21139-1
related SUSE-SU-2025:21179-1
related SUSE-SU-2025:4123-1
related SUSE-SU-2026:0688-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2025-38177

In the Linux kernel, the following vulnerability has been resolved: sch_hfsc: make hfsc_qlen_notify() idempotent hfsc_qlen_notify() is not idempotent either and not friendly to its callers, like fq_codel_dequeue(). Let's make it idempotent to ease qdisc_tree_reduce_backlog() callers' life: 1. update_vf() decreases cl->cl_nactive, so we can check whether it is non-zero before calling it. 2. eltree_remove() always removes RB node cl->el_node, but we can use RB_EMPTY_NODE() + RB_CLEAR_NODE() to make it safe.

View original source

05 / REFERENCES

Further evidence