---
id: CVE-2026-90390
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  md/bitmap: resume array on backlog_store() error path

  backlog_store() suspends the array before checking whether a write-mostly
  device exists
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  md/bitmap: resume array on backlog_store() error path

  backlog_store() suspends the array before checking whether a write-mostly
  device exists. If no such device exists…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 58226942ad3d1423785f815ede5bcc832574f2ea <
    03aad318f0a1f039dddf98739e705fdca3bf0d86
  - >-
    Linux >= 58226942ad3d1423785f815ede5bcc832574f2ea <
    6763fb409a0b4106676a52cf934440d9484b32c8
  - >-
    Linux >= 58226942ad3d1423785f815ede5bcc832574f2ea <
    cc543e769b97d563b089b9e0ebf8ad361d15076f
  - >-
    Linux >= 58226942ad3d1423785f815ede5bcc832574f2ea <
    2911cd0a0f4366a7e06832bc5f0a7fdcc138e4dc
  - Linux 6.7
published: '2026-09-17'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T17:17:38.530'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-90390'
references:
  - url: 'https://git.kernel.org/stable/c/03aad318f0a1f039dddf98739e705fdca3bf0d86'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2911cd0a0f4366a7e06832bc5f0a7fdcc138e4dc'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6763fb409a0b4106676a52cf934440d9484b32c8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/cc543e769b97d563b089b9e0ebf8ad361d15076f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-17T16:21:47.803Z'
epss: 0.00209
epssPercentile: 0.09855
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

md/bitmap: resume array on backlog_store() error path

backlog_store() suspends the array before checking whether a write-mostly
device exists. If no such device exists, the error path only unlocks
reconfig_mutex and leaves the array suspended, blocking subsequent I/O.

Use mddev_unlock_and_resume() to release both states.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.