<?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://db.gcve.eu</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>Wed, 30 Sep 2026 14:34:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93146 — time/namespace: Validate nanosecond field in proc_timens_set_offset()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-93146</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;time/namespace: Validate nanosecond field in proc_timens_set_offset()&lt;/p&gt;
&lt;p&gt;The function validates tv_sec to be within [-KTIME_SEC_MAX, KTIME_SEC_MAX]
but never validates that tv_nsec is within the valid range of
[0, NSEC_PER_SEC-1] before using it in timespec64_add().&lt;/p&gt;
&lt;p&gt;timespec64_add() expects both timespec64 structures to have normalized
values with tv_nsec in the range [0, 999999999]. If off-&amp;gt;val.tv_nsec
contains invalid values (negative or &amp;gt;= NSEC_PER_SEC), it could lead to
incorrect calculations or unexpected behavior.&lt;/p&gt;
&lt;p&gt;Add validation to ensure tv_nsec is within the valid range before
performing the addition.&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;time/namespace: Validate nanosecond field in proc_timens_set_offset()&lt;/p&gt;
&lt;p&gt;The function validates tv_sec to be within [-KTIME_SEC_MAX, KTIME_SEC_MAX]
but never validates that tv_nsec is within the valid range of
[0, NSEC_PER_SEC-1] before using it in timespec64_add().&lt;/p&gt;
&lt;p&gt;timespec64_add() expects both timespec64 structures to have normalized
values with tv_nsec in the range [0, 999999999]. If off-&amp;gt;val.tv_nsec
contains invalid values (negative or &amp;gt;= NSEC_PER_SEC), it could lead to
incorrect calculations or unexpected behavior.&lt;/p&gt;
&lt;p&gt;Add validation to ensure tv_nsec is within the valid range before
performing the addition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-93146</guid>
    </item>
  </channel>
</rss>
