CVE-2026-93261

Description

A flaw was found in the Linux kernel's lock dependency validator (lockdep). When lock class registration fails, the kernel omits a check for an empty result before calculating internal index values, leading to memory corruption. A local user can exploit this vulnerability during lock reacquisition to cause an invalid memory dereference, resulting in a kernel crash and Denial of Service (DoS).

Statement

A flaw of moderate impact was found in the Linux kernel's lock dependency validator (lockdep). When register_lock_class() fails and returns NULL - for example when the lock class pool is exhausted, the graph lock cannot be acquired, or lock key validation fails - __lock_set_class() uses the NULL return value in pointer arithmetic without first checking it, which corrupts the held lock's internal class index. A subsequent reacquire_held_locks() operation then dereferences that corrupted index, causing a NULL or out-of-bounds memory dereference that crashes the kernel. A local user able to run code on the system can trigger this code path to cause a denial of service; the flaw has no confidentiality or integrity impact. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those kernels. The fix is currently deferred for the affected Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform (RHEL CoreOS) streams; the residual risk of the deferral is limited to local denial of service, since exploitation requires local code execution and a lock class registration failure such as pool exhaustion or key validation failure within the lockdep validator.

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

NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.

Integrity,Confidentiality

Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory

In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.

Frequently Asked Questions

Want to get errata notifications? Sign up here.