LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46095: md/md-llbitmap: raise barrier before state machine transition

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-46095 is a Linux kernel storage-layer race condition in md/md-llbitmap. The fix changes operation ordering so a barrier is raised before state transitions during write and discard handling. Public sources do not provide CVSS, confirmed impact, or evidence of active exploitation.

Executive priority

Treat as a kernel maintenance item for storage-relevant Linux systems. Urgency is constrained by missing severity and no cited exploitation, but kernel race conditions in storage code can have operational consequences, so include it in the next controlled patch cycle.

Technical view

In llbitmap_start_write() and llbitmap_start_discard(), the barrier raise was moved before llbitmap_state_machine(). The stated issue is a potential race where the state machine could complete before the barrier is raised. Linux stable commit references are provided as remediation evidence.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions that use the md/md-llbitmap code path, likely storage configurations involving Linux md behavior. The source bundle lists affected Linux versions but does not provide distribution package mappings or exploit prerequisites.

Exploitation context

No KEV listing is reported, and the supplied sources do not claim active exploitation. The public description frames the issue as a race condition fixed in kernel code, without describing attacker control, privilege requirements, or demonstrated impact.

Researcher notes

Key unknowns are exploitability, impact class, affected configurations, and distro backport status. Analysis should focus on md/md-llbitmap use, the ordering change around llbitmap_state_machine(), and whether write or discard paths can produce reliability or security impact.

Mitigation direction

  • Check Linux vendor advisories for packaged kernel fixes for CVE-2026-46095.
  • Update affected kernels to versions containing the referenced stable fixes.
  • Prioritize systems using Linux md storage features until impact is clarified.
  • Track distribution backports because package versions may differ from upstream kernel versions.

Validation and detection

  • Inventory kernel versions against the affected version data in the CVE record.
  • Confirm whether systems use Linux md storage paths relevant to md-llbitmap.
  • Verify fixed kernels include one of the referenced stable commits or vendor backports.
  • Review change records for storage hosts before and after kernel updates.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46095 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5ab829f1971dc99f2aac10846c378e67fc875abc, 5ab829f1971dc99f2aac10846c378e67fc875abc, 5ab829f1971dc99f2aac10846c378e67fc875abcunaffected
LinuxLinux6.18, 0, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.