<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T11:08:15.544795+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2025-38177</id>
    <title>CVE-2025-38177 — sch_hfsc: make hfsc_qlen_notify() idempotent</title>
    <updated>2026-09-30T11:08:15.546942+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>sch_hfsc: make hfsc_qlen_notify() idempotent</p>
<p>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:</p>
<p>1. update_vf() decreases cl-&gt;cl_nactive, so we can check whether it is
non-zero before calling it.</p>
<p>2. eltree_remove() always removes RB node cl-&gt;el_node, but we can use
   RB_EMPTY_NODE() + RB_CLEAR_NODE() to make it safe.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-38177"/>
  </entry>
</feed>
