LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46045: md/md-llbitmap: skip reading rdevs that are not in_sync

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can make software RAID read recovery bitmap data from a spare disk that is still rebuilding. That disk may contain stale or uninitialized bitmap information, causing the RAID layer to track dirty data incorrectly. The business concern is data integrity, especially during rebuilds or recovery, not remote code execution.

Executive priority

Treat this as a data-integrity maintenance priority for Linux storage platforms, not an emergency internet-facing exposure. Patch during the next suitable maintenance window, sooner for systems with active RAID rebuilds, critical data, or limited backup tolerance.

Technical view

The md/md-llbitmap code selected member disks for bitmap page reads by checking raid_disk assignment and Faulty state, but not In_sync. A rebuilding spare could therefore be used as a bitmap source before it held valid bitmap data. The fix adds the In_sync check so bitmap pages are read only from synchronized RAID members.

Likely exposure

Exposure is likely limited to Linux systems using md software RAID with llbitmap behavior, especially arrays involving spares, rebuilds, or recovery. The provided record does not identify distributions, appliances, cloud images, or configurations beyond Linux kernel md.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The issue appears to be an operational data-integrity bug triggered by RAID state handling, not an attacker-driven remote compromise path. Evidence for practical exploitation is incomplete.

Researcher notes

The public record describes the root cause and fix direction but provides no CVSS, CWE, distro matrix, or exploit evidence. Analysis should stay scoped to md/md-llbitmap member selection and the missing In_sync check.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Prioritize systems using Linux md software RAID with bitmaps and hot spares.
  • Follow Linux kernel and distribution advisories for fixed package versions.
  • Avoid unnecessary RAID rebuild or recovery churn until patched where operationally feasible.

Validation and detection

  • Inventory Linux hosts that use md software RAID and bitmap tracking.
  • Check whether running kernels include one of the referenced stable commits.
  • Review RAID arrays for recent rebuild, spare promotion, or recovery activity.
  • Monitor storage integrity alerts and md recovery logs after patching.
Prepared
Confidence
medium
Sources
5

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-46045 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.

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.