<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T12:18:18.419708+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-93146</id>
    <title>CVE-2026-93146 — time/namespace: Validate nanosecond field in proc_timens_set_offset()</title>
    <updated>2026-09-30T12:18:18.431403+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>time/namespace: Validate nanosecond field in proc_timens_set_offset()</p>
<p>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().</p>
<p>timespec64_add() expects both timespec64 structures to have normalized
values with tv_nsec in the range [0, 999999999]. If off-&gt;val.tv_nsec
contains invalid values (negative or &gt;= NSEC_PER_SEC), it could lead to
incorrect calculations or unexpected behavior.</p>
<p>Add validation to ensure tv_nsec is within the valid range before
performing the addition.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-93146"/>
  </entry>
</feed>
