CVE-2026-72068 — posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < feb5c87c8514444ba891b75a5a3eae57c64edaf8≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < 384628d6cdde0fcd76868606fad3ad8293100afb≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < 1fafc4d9b411645eb34de43362b966dc8fb3e263≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < cff8281bacd2866767e6194c3079d33b6c5a74f4≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < edf6babb9edd2d3e19229ade339081f439d4f478≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < ea6a188ee805e841a0e242f14d15953e0dfa74bb≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < 571e1f10b5996ba3e4dc63ea77de4aa309c384ce≥ 858cf3a8c59968e7c5f7c1a1192459a0d52d1ab4 and < 26aff38fefb1d6cd87e22525f41cc8f1aa61b24f and 1 moreversion 4.11 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/384628d6cdde0fcd76868606fad3ad8293100afb
- git.kernel.org/stable/c/571e1f10b5996ba3e4dc63ea77de4aa309c384ce
- git.kernel.org/stable/c/feb5c87c8514444ba891b75a5a3eae57c64edaf8
- git.kernel.org/stable/c/26aff38fefb1d6cd87e22525f41cc8f1aa61b24f
- git.kernel.org/stable/c/ea6a188ee805e841a0e242f14d15953e0dfa74bb
- git.kernel.org/stable/c/1fafc4d9b411645eb34de43362b966dc8fb3e263
- git.kernel.org/stable/c/cff8281bacd2866767e6194c3079d33b6c5a74f4
- git.kernel.org/stable/c/edf6babb9edd2d3e19229ade339081f439d4f478
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72068 is "posix-cpu-timers: Use u64 multiplication in update_rlimit_cpu()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.