CVE-2026-72068
Description
A flaw was found in the Linux kernel's posix-cpu-timers component on 32-bit systems. An integer truncation vulnerability occurs in the update_rlimit_cpu() function when converting the RLIMIT_CPU value to nanoseconds. This issue causes the process CPU timer to be programmed to fire prematurely for RLIMIT_CPU soft limits of 5 seconds or more. While actual resource limit enforcement remains correct, this premature timer expiry could lead to a denial of service for affected processes.
Statement
A low-impact integer truncation flaw was found in the Linux kernel's posix-cpu-timers subsystem, affecting Red Hat Enterprise Linux and Red Hat In-Vehicle OS only on 32-bit architectures. In update_rlimit_cpu(), the RLIMIT_CPU soft limit is converted to nanoseconds with a 32-bit multiplication that truncates the result for limits greater than 4 seconds. The truncated value is installed in the CPUCLOCK_PROF expiry cache, so the process CPU timer is programmed to fire prematurely for RLIMIT_CPU soft limits of 5 seconds or more, causing premature delivery of SIGXCPU/SIGKILL and a limited denial of service against affected processes. The actual limit enforcement decision in check_process_timers() already uses 64-bit arithmetic and remains correct, so the CPU limit is not bypassed; exploitation requires a local process to set its own RLIMIT_CPU, and 64-bit kernels are unaffected. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those streams. For affected Red Hat Enterprise Linux 8, 9, and 10 update streams and Red Hat In-Vehicle OS streams, the fix is deferred because the impact is low and resource limit enforcement remains correct; the residual risk is limited to premature CPU timer signal delivery on 32-bit systems. Red Hat rates the impact of this flaw as Low even though the CVSS:3.1 base score of 5.5 suggests Moderate, because the flaw only degrades CPU timer expiry-cache accuracy on 32-bit systems and does not weaken actual resource limit enforcement or affect confidentiality or integrity.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Access Control
Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart
If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.