<?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://cve.radiocsirt.org</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, 06 Oct 2026 22:40:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80927 — timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-80927</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;timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()&lt;/p&gt;
&lt;p&gt;If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled
before tks-&amp;gt;clock_valid is checked, then uninitialized stackdata will be
used in the calculations and indirectly leaked to userspace.&lt;/p&gt;
&lt;p&gt;The same race window also exists after this change and also for the core
timekeeper. But in these cases the only effect would be incorrect
adjustments and this is userspace&amp;#39;s responsibility to avoid this.&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;timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()&lt;/p&gt;
&lt;p&gt;If the auxiliary clock is disabled during tk_get_aux_ts64() but is enabled
before tks-&amp;gt;clock_valid is checked, then uninitialized stackdata will be
used in the calculations and indirectly leaked to userspace.&lt;/p&gt;
&lt;p&gt;The same race window also exists after this change and also for the core
timekeeper. But in these cases the only effect would be incorrect
adjustments and this is userspace&amp;#39;s responsibility to avoid this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-80927</guid>
    </item>
  </channel>
</rss>
