<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 04:54:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74670 — ipvs: stop estimator after disabled calc phase</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74670</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipvs: stop estimator after disabled calc phase&lt;/p&gt;
&lt;p&gt;IPVS estimator kthread 0 starts with zeroed chain and tick limits until
its initial calculation phase completes. If network namespace teardown
clears ipvs-&amp;gt;enable during that phase, ip_vs_est_calc_phase() can return
without installing positive limits.&lt;/p&gt;
&lt;p&gt;The kthread can then continue into its main loop and drain
est_temp_list with zero chain_max, tick_max and est_max_count values.
Each enqueue consumes one available tick row, but est_count never
reaches the zero est_max_count value. After all rows are consumed, the
row lookup returns IPVS_EST_NTICKS and ip_vs_enqueue_estimator() writes
past the ticks and tick_len arrays.&lt;/p&gt;
&lt;p&gt;Exit kthread 0 after the calculation phase if the kthread is stopping or
IPVS has been disabled. That keeps temporary estimators from being
drained after the limits failed to initialize.&lt;/p&gt;
&lt;p&gt;Estimator kthreads can now self-exit before teardown or reload stops
kd-&amp;gt;task. Keep an extra task reference after creation and release it
with kthread_stop_put(), so kd-&amp;gt;task remains valid until the stop paths
consume that reference.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipvs: stop estimator after disabled calc phase&lt;/p&gt;
&lt;p&gt;IPVS estimator kthread 0 starts with zeroed chain and tick limits until
its initial calculation phase completes. If network namespace teardown
clears ipvs-&amp;gt;enable during that phase, ip_vs_est_calc_phase() can return
without installing positive limits.&lt;/p&gt;
&lt;p&gt;The kthread can then continue into its main loop and drain
est_temp_list with zero chain_max, tick_max and est_max_count values.
Each enqueue consumes one available tick row, but est_count never
reaches the zero est_max_count value. After all rows are consumed, the
row lookup returns IPVS_EST_NTICKS and ip_vs_enqueue_estimator() writes
past the ticks and tick_len arrays.&lt;/p&gt;
&lt;p&gt;Exit kthread 0 after the calculation phase if the kthread is stopping or
IPVS has been disabled. That keeps temporary estimators from being
drained after the limits failed to initialize.&lt;/p&gt;
&lt;p&gt;Estimator kthreads can now self-exit before teardown or reload stops
kd-&amp;gt;task. Keep an extra task reference after creation and release it
with kthread_stop_put(), so kd-&amp;gt;task remains valid until the stop paths
consume that reference.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74670</guid>
    </item>
  </channel>
</rss>
