md: wait for behind writes before destroying bitmap (CVE-2026-90278) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90278

md: wait for behind writes before destroying bitmap

Answer in brief

CVE-2026-90278 records a Unknown severity vulnerability in md: wait for behind writes before destroying bitmap. 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.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

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.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=5ab829f1971dc99f2aac10846c378e67fc875abc <73881ff7a75913f919a1ce9d9571bfaab8e8588d \|\| >=5ab829f1971dc99f2aac10846c378e67fc875abc <4224dccd325a9380e8edfb66aad8bb5771c94222 \|\| >=5ab829f1971dc99f2aac10846c378e67fc875abc <2a79365b2278f16e163e4024086105693b421601	73881ff7a75913f919a1ce9d9571bfaab8e8588d, 4224dccd325a9380e8edfb66aad8bb5771c94222, 2a79365b2278f16e163e4024086105693b421601
Linux/Linuxgeneric	6.18	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 73881ff7a75913f919a1ce9d9571bfaab8e8588d if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: md: wait for behind writes before destroying bitmap __md_stop() destroyed the bitmap before calling mddev_detach(). That made mddev_detach() skip bitmap_ops->wait_behind_writes(), because the bitmap was already disconnected from mddev. This was still safe for the legacy bitmap because bitmap_destroy() waits for behind writes itself. llbitmap keeps that wait in its ->wait_behind_writes() operation instead, while ->destroy() tears down the llbitmap storage. With the old ordering, RAID1 behind-write completions could still run after llbitmap storage had been freed. Call mddev_detach() before md_bitmap_destroy() so the common detach path can wait for behind writes while the bitmap is still alive. Only destroy the bitmap after those users are gone.

Quoted source text, attributed separately from HOL analysis.