Barrier Synchronization Flaw in Linux Kernel md-llbitmap

Publication date: 2026-05-27

Last updated on: 2026-06-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: md/md-llbitmap: raise barrier before state machine transition Move the barrier raise operation before calling llbitmap_state_machine() in both llbitmap_start_write() and llbitmap_start_discard(). This ensures the barrier is in place before any state transitions occur, preventing potential race conditions where the state machine could complete before the barrier is properly raised.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-25

Generated

2026-07-07

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-46095

EUVD

EUVD-2026-32478

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.19 (inc) to 7.0.4 (exc)
linux	linux_kernel	From 6.18 (inc) to 6.18.27 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel relates to the md/md-llbitmap component. The issue involves the order of operations in the code where a barrier raise operation was performed after calling the state machine transition function llbitmap_state_machine(). The fix moves the barrier raise operation to occur before the state machine transition. This change prevents potential race conditions where the state machine could complete before the barrier is properly raised.

Impact Analysis

The vulnerability could lead to race conditions in the Linux kernel's md/md-llbitmap component. Such race conditions might cause unexpected behavior or instability in the system, potentially affecting data integrity or system reliability where the md-llbitmap functionality is used.

Hi! I’m here to help you understand CVE-2026-46095. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70