<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T01:49:09.322806+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-31574</id>
    <title>CVE-2026-31574 — clockevents: Add missing resets of the next_event_forced flag</title>
    <updated>2026-10-02T01:49:09.323789+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>clockevents: Add missing resets of the next_event_forced flag</p>
<p>The prevention mechanism against timer interrupt starvation missed to reset
the next_event_forced flag in a couple of places:</p>
<p>- When the clock event state changes. That can cause the flag to be
      stale over a shutdown/startup sequence</p>
<p>- 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.</p>
<p>- In the suspend wakeup handler.</p>
<p>That led to stalls which have been reported by several people.</p>
<p>Add the missing resets, which fixes the problems for the reporters.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31574"/>
  </entry>
</feed>
