CVE-2026-72068None▾ SunlitIn 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 * N…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < feb5c87c8514444ba891b75a5a3eae57c64edaf8Linux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < 384628d6cdde0fcd76868606fad3ad8293100afbLinux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < 1fafc4d9b411645eb34de43362b966dc8fb3e263Linux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < cff8281bacd2866767e6194c3079d33b6c5a74f4Linux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < edf6babb9edd2d3e19229ade339081f439d4f478Linux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < ea6a188ee805e841a0e242f14d15953e0dfa74bbLinux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < 571e1f10b5996ba3e4dc63ea77de4aa309c384ceLinux >= 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 < 26aff38fefb1d6cd87e22525f41cc8f1aa61b24fLinux 4.11Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses