<?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 11:28:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52633 — um: time-travel: fix time corruption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52633</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;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&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;um: time-travel: fix time corruption&lt;/p&gt;
&lt;p&gt;In &amp;#39;basic&amp;#39; time-travel mode (without =inf-cpu or =ext), we
still get timer interrupts. These can happen at arbitrary
points in time, i.e. while in timer_read(), which pushes
time forward just a little bit. Then, if we happen to get
the interrupt after calculating the new time to push to,
but before actually finishing that, the interrupt will set
the time to a value that&amp;#39;s incompatible with the forward,
and we&amp;#39;ll crash because time goes backwards when we do the
forwarding.&lt;/p&gt;
&lt;p&gt;Fix this by reading the time_travel_time, calculating the
adjustment, and doing the adjustment all with interrupts
disabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52633</guid>
    </item>
  </channel>
</rss>
