CVE-2026-72068

Not scored yetLast modified Nov 6, 2026

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < feb5c87c8514444ba891b75a5a3eae57c64edaf8; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < 384628d6cdde0fcd76868606fad3ad8293100afb; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < 1fafc4d9b411645eb34de43362b966dc8fb3e263; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < cff8281bacd2866767e6194c3079d33b6c5a74f4; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < edf6babb9edd2d3e19229ade339081f439d4f478; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < ea6a188ee805e841a0e242f14d15953e0dfa74bb; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < 571e1f10b5996ba3e4dc63ea77de4aa309c384ce; >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4, < 26aff38fefb1d6cd87e22525f41cc8f1aa61b24f
LinuxLinux4.11

References

Timeline

Published
Aug 15, 2026
Last modified
Nov 6, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-720699.8In the Linux kernel, the following vulnerability has been resolved: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() rt_spCVE-2026-72070In the Linux kernel, the following vulnerability has been resolved: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() lbtf_freeCVE-2026-720717.8In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Fix use-after-free in user_event_mm_dup() user_evCVE-2026-720727.8In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete CVE-2026-72073In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: fix use-after-free on probe failure The vub300 driver lifCVE-2026-72074In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix type confusion in CDC union descriptor parsing ThCVE-2026-72075In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix race condition in reset_device sysfs callback TheCVE-2026-72076In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging CVE-2026-72077In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix firmware leak in async update The firmware objectCVE-2026-72078In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - validate control endpoint type The driver currently aCVE-2026-72079In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix use-after-free and double-free in disconnect ims_CVE-2026-72085.3Yealink SIP-T33G firmware versions 124.86.x.x prior to 124.87.0.0 contain a race condition vulnerability that allows authenticated attackers
CVE-2026-72068: Unscored | Vulnix