<?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-02T19:55:08.465324+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-72068</id>
    <title>CVE-2026-72068 — posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()</title>
    <updated>2026-10-02T19:55:08.468560+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>posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()</p>
<p>update_rlimit_cpu() converts the RLIMIT_CPU value to nanoseconds with</p>
<p>u64 nsecs = rlim_new * NSEC_PER_SEC;</p>
<p>On 32-bit kernels both rlim_new (unsigned long) and NSEC_PER_SEC
(1000000000L) are 32-bit, so the multiplication is performed in unsigned
long and truncated for rlim_new &gt; 4 seconds before being widened to u64.</p>
<p>The same file already casts to u64 for the matching computation in
check_process_timers():</p>
<p>u64 softns = (u64)soft * NSEC_PER_SEC;</p>
<p>As a result, the truncated value is installed into the CPUCLOCK_PROF
expiry cache (nextevt), causing the process CPU timer to be programmed
to fire prematurely for any RLIMIT_CPU soft limit &gt;= 5 seconds. The
actual SIGXCPU/SIGKILL decision in check_process_timers() already casts
to u64 and is therefore correct, so limit enforcement is not broken;
only the expiry-cache programming is wrong. Apply the same cast here so
both paths convert rlim_cur identically.</p>
<p>64-bit kernels are unaffected.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-72068"/>
  </entry>
</feed>
