CVE-2026-98412
Description
A flaw was found in the Linux kernel's power sequencing subsystem. If a memory allocation failure occurs while setting up dependencies in pwrseq_unit_setup_deps(), error handling cleans up the partially allocated unit without having initialized its internal list. This uninitialized state leads to a NULL pointer dereference during cleanup, causing a kernel crash and resulting in a Denial of Service (DoS).
Statement
A flaw of moderate impact was found in the Linux kernel power sequencing subsystem (drivers/power/sequencing/core.c) as shipped in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2. If a memory allocation fails while setting up unit dependencies in pwrseq_unit_setup_deps(), the error path releases the partially initialized unit, and pwrseq_unit_release() unconditionally calls list_del() on the unit's not-yet-initialized list, causing a NULL pointer dereference that crashes the kernel (denial of service). Exploiting this requires privileged local access to the system and depends on an unexpected memory allocation failure during power sequencing unit setup, which is reflected in the Red Hat CVSS 3.1 score of 4.1 (AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H); only availability is impacted. Fixes for the affected Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 kernels are deferred to a future planned update because this is a low-severity, hard-to-trigger error-path defect; the residual risk is that a local privileged user who can induce the allocation failure could crash the system. Earlier Red Hat Enterprise Linux versions (including kernel and kernel-rt in RHEL 6 through 9) and the OpenShift Container Platform RHEL CoreOS images are not affected because the vulnerable code, introduced upstream in the 6.11 kernel, is not present in those products.
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 | 4.1 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | High | 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:H/PR:H/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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.