VulnerabilityPublished 27 May 2026Updated 6 Nov 2026

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

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in 98623c7e2a51eab1833c8628d33fa9c6ef3ce325 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in 98623c7e2a51eab1833c8628d33fa9c6ef3ce325, 7701e68b5072faa03a8f30b4081dc16df9092381, 3115fa2f62970d98f2a639145fb8e2767db8bbf9

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 98623c7e2a51eab1833c8628d33fa9c6ef3ce325, 7701e68b5072faa03a8f30b4081dc16df9092381 or 3115fa2f62970d98f2a639145fb8e2767db8bbf9.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 5ab829f1971dc99f2aac10846c378e67fc875abc, < 98623c7e2a51eab1833c8628d33fa9c6ef3ce325	Fixed in 98623c7e2a51eab1833c8628d33fa9c6ef3ce325
LinuxLinux	Affected ≥ 5ab829f1971dc99f2aac10846c378e67fc875abc, < 7701e68b5072faa03a8f30b4081dc16df9092381	Fixed in 7701e68b5072faa03a8f30b4081dc16df9092381
LinuxLinux	Affected ≥ 5ab829f1971dc99f2aac10846c378e67fc875abc, < 3115fa2f62970d98f2a639145fb8e2767db8bbf9	Fixed in 3115fa2f62970d98f2a639145fb8e2767db8bbf9
LinuxLinux	Affected =6.18	Fixed in–

Description

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.

References

Community reviews

Loading reviews…