<?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>Fri, 02 Oct 2026 01:49:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31574 — clockevents: Add missing resets of the next_event_forced flag</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31574</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;clockevents: Add missing resets of the next_event_forced flag&lt;/p&gt;
&lt;p&gt;The prevention mechanism against timer interrupt starvation missed to reset
the next_event_forced flag in a couple of places:&lt;/p&gt;
&lt;p&gt;- When the clock event state changes. That can cause the flag to be
      stale over a shutdown/startup sequence&lt;/p&gt;
&lt;p&gt;- When a non-forced event is armed, which then prevents rearming before
      that event. If that event is far out in the future this will cause
      missed timer interrupts.&lt;/p&gt;
&lt;p&gt;- In the suspend wakeup handler.&lt;/p&gt;
&lt;p&gt;That led to stalls which have been reported by several people.&lt;/p&gt;
&lt;p&gt;Add the missing resets, which fixes the problems for the reporters.&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;clockevents: Add missing resets of the next_event_forced flag&lt;/p&gt;
&lt;p&gt;The prevention mechanism against timer interrupt starvation missed to reset
the next_event_forced flag in a couple of places:&lt;/p&gt;
&lt;p&gt;- When the clock event state changes. That can cause the flag to be
      stale over a shutdown/startup sequence&lt;/p&gt;
&lt;p&gt;- When a non-forced event is armed, which then prevents rearming before
      that event. If that event is far out in the future this will cause
      missed timer interrupts.&lt;/p&gt;
&lt;p&gt;- In the suspend wakeup handler.&lt;/p&gt;
&lt;p&gt;That led to stalls which have been reported by several people.&lt;/p&gt;
&lt;p&gt;Add the missing resets, which fixes the problems for the reporters.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31574</guid>
    </item>
  </channel>
</rss>
