CVE-2026-98398
Description
A flaw was found in the Linux kernel's lock dependency validator (lockdep). When a lock class is removed, such as during kernel module unloading, cached references in existing lock structures are not properly cleared. A local user can exploit this issue by triggering lock acquisitions that reuse these stale references, resulting in an inconsistent tracking state. This flaw can lead to kernel warnings, disabled lock validation, and potentially a Denial of Service (DoS) via a system crash.
Statement
A LOW impact flaw was found in the Linux kernel's lock dependency validator (lockdep), affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10, the kernel packages in Red Hat In-Vehicle OS, and the RHEL CoreOS kernels used by OpenShift Container Platform 4. When a lock class is removed, for example during kernel module unload or lock key unregistration, cached class pointers (class_cache entries) stored in existing lockdep_map structures are not invalidated. A local user can trigger lock acquisitions that reuse these stale references, resulting in an invalid class index and an inconsistent lock tracking state. This leads to lockdep DEBUG_LOCKS_WARN_ON kernel warnings, can disable lock validation, and can potentially cause a denial of service through a system crash on systems configured to panic on warnings. Confidentiality and integrity are not affected: the demonstrated effect is stale lockdep diagnostic metadata rather than a memory corruption or arbitrary write primitive, which is why Red Hat rates the impact of this flaw as LOW even though the CVSS 3.1 base score of 5.5 reflects a high availability impact. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those kernels. Because this issue is confined to the lockdep debugging infrastructure, does not provide a memory corruption or privilege escalation primitive, and the stale state arises from operations such as module unloading or lock key unregistration, the fix is currently deferred for the affected products. The residual risk of deferring the fix is limited to lockdep warnings, disabled lock validation, and a possible kernel crash (denial of service), particularly on systems configured with panic_on_warn.
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)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.