CVE-2026-90157

Description

A flaw was found in the Linux kernel. A local attacker could exploit a vulnerability in the BPF (Berkeley Packet Filter) cgroup getsockopt hook. By providing a negative length value, a malicious BPF program could cause the kernel's memory copy function to process an invalid size. This could lead to a system crash, resulting in a denial of service.

Statement

A moderate severity denial of service flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) cgroup getsockopt hook. A cgroup getsockopt BPF program can set a negative ctx->optlen after the kernel getsockopt handler has run; the kernel-buffer variant of this hook, used by TCP_ZEROCOPY_RECEIVE, only rejects values larger than the original length, so a negative optlen is accepted and propagated back to the TCP getsockopt code. The negative value can then be passed to copy_to_sockptr() as a size_t and trigger the hardened usercopy bytes > INT_MAX check, resulting in a system crash. Exploitation requires local access with the privileges needed to load and attach a malicious cgroup getsockopt BPF program, and a successful attack affects system availability only. This issue affects the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS, and the RHEL CoreOS kernels shipped with OpenShift 4. Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, and the Red Hat Enterprise Linux 8.4 z-stream are not affected because the vulnerable code is not present in those kernels. Fixes for the affected streams are currently deferred: since exploitation requires an already-privileged local user and the consequence is limited to loss of availability, the residual risk of deferral is low and consists of a potential local system crash (denial of service).

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 HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/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

Want to get errata notifications? Sign up here.