CVE-2026-90278
Description
A flaw was found in the Linux kernel's Multiple Device (MD) driver, specifically in how it handles bitmap destruction. When the __md_stop() function was called, it destroyed the bitmap before ensuring all pending write operations were complete. This could lead to RAID1 behind-write completions attempting to access freed memory, resulting in memory corruption. An attacker could potentially leverage this to cause system instability or a denial of service.
Statement
md __md_stop() could destroy the bitmap before mddev_detach() had a chance to wait for RAID1 behind write completions. With llbitmap, the wait is implemented in wait_behind_writes() while destroy() tears down the llbitmap storage, so completions may run after the storage has been freed. This is a local race and use-after-free candidate in the md storage path and can at least cause denial of service via kernel crash or corrupted md bitmap state. For the CVSS the PR:L is used for the paranoid score because md control may be delegated to a storage management service, reduced capability root, or another local process with limited but relevant administrative access. The issue is not directly network reachable and requires local control of md stop or detach behavior plus outstanding behind writes. Impact is at least local denial of service.
Mitigation
Mitigation for this issue is either not available or the currently available options don't 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)
Integrity
Technical Impact: Modify Memory
The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.
Confidentiality
Technical Impact: Read Memory
Read operations on freed memory can sometimes leak sensitive information instead of causing a crash
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.