CVE-2026-72068

posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()

N/A
Published: August 15, 2026 at 05:52 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu() update_rlimit_cpu() converts the RLIMIT_CPU value to nanoseconds with u64 nsecs = rlim_new * NSEC_PER_SEC; 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 > 4 seconds before being widened to u64. The same file already casts to u64 for the matching computation in check_process_timers(): u64 softns = (u64)soft * NSEC_PER_SEC; 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 >= 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. 64-bit kernels are unaffected.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.11 ≤ v < 5.10.2614.11 ≤ v < 5.15.2124.11 ≤ v < 6.1.1784.11 ≤ v < 6.12.974.11 ≤ v < 6.18.404.11 ≤ v < 6.6.1454.11 ≤ v < 7.1.54.11 ≤ v < 7.24.11858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4
Vendor states this is fixed in 1fafc4d9b411645eb34de43362b966dc8fb3e263 (fixed)
Vendor states this is fixed in 26aff38fefb1d6cd87e22525f41cc8f1aa61b24f (fixed)
Vendor states this is fixed in 384628d6cdde0fcd76868606fad3ad8293100afb (fixed)
Vendor states this is fixed in 571e1f10b5996ba3e4dc63ea77de4aa309c384ce (fixed)
Vendor states this is fixed in cff8281bacd2866767e6194c3079d33b6c5a74f4 (fixed)
Vendor states this is fixed in ea6a188ee805e841a0e242f14d15953e0dfa74bb (fixed)
Vendor states this is fixed in edf6babb9edd2d3e19229ade339081f439d4f478 (fixed)
Vendor states this is fixed in feb5c87c8514444ba891b75a5a3eae57c64edaf8 (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card