Answer in brief
CVE-2026-46045 records a Unknown severity vulnerability in md/md-llbitmap: skip reading rdevs that are not in_sync. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5ab829f1971dc99f2aac10846c378e67fc875abc <98623c7e2a51eab1833c8628d33fa9c6ef3ce325 || >=5ab829f1971dc99f2aac10846c378e67fc875abc <3115fa2f62970d98f2a639145fb8e2767db8bbf9 || >=5ab829f1971dc99f2aac10846c378e67fc875abc <7701e68b5072faa03a8f30b4081dc16df9092381 | 98623c7e2a51eab1833c8628d33fa9c6ef3ce325, 3115fa2f62970d98f2a639145fb8e2767db8bbf9, 7701e68b5072faa03a8f30b4081dc16df9092381 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
In the Linux kernel, the following vulnerability has been resolved: md/md-llbitmap: skip reading rdevs that are not in_sync When reading bitmap pages from member disks, the code iterates through all rdevs and attempts to read from the first available one. However, it only checks for raid_disk assignment and Faulty flag, missing the In_sync flag check. This can cause bitmap data to be read from spare disks that are still being rebuilt and don't have valid bitmap information yet. Reading stale or uninitialized bitmap data from such disks can lead to incorrect dirty bit tracking, potentially causing data corruption during recovery or normal operation. Add the In_sync flag check to ensure bitmap pages are only read from fully synchronized member disks that have valid bitmap data.
Quoted source text, attributed separately from HOL analysis.