CVE-2026-46045

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

md/md-llbitmap: skip reading rdevs that are not in_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98623c7e2a51eab1833c8628d33fa9c6ef3ce325
generic

md/md-llbitmap: skip reading rdevs that are not in_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7701e68b5072faa03a8f30b4081dc16df9092381
generic

md/md-llbitmap: skip reading rdevs that are not in_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3115fa2f62970d98f2a639145fb8e2767db8bbf9

Vendor Advisories for CVE-2026-46045(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 232 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 08:16 UTCEG score recompute
  3. 2026-09-14 08:16 UTCVendor advisory
  4. 2026-09-14 08:16 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 03:39 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 05:24 UTCEG score recompute
  23. 2026-08-25 05:24 UTCVendor advisory
  24. 2026-08-25 05:24 UTCGHSA enrichment
  25. 2026-08-23 15:10 UTCEG score recompute
Show 75 more
  1. 2026-08-23 15:10 UTCVendor advisory
  2. 2026-08-23 15:10 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 20:40 UTCVendor advisory
  5. 2026-08-21 20:40 UTCGHSA enrichment
  6. 2026-08-21 01:38 UTCEG score recompute
  7. 2026-08-21 01:38 UTCVendor advisory
  8. 2026-08-21 01:38 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 11:26 UTCEG score recompute
  11. 2026-08-20 11:26 UTCVendor advisory
  12. 2026-08-20 11:26 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:18 UTCVendor advisory
  17. 2026-08-17 09:18 UTCGHSA enrichment
  18. 2026-08-16 15:14 UTCVendor advisory
  19. 2026-08-16 15:14 UTCGHSA enrichment
  20. 2026-08-16 02:51 UTCEG score recompute
  21. 2026-08-16 02:51 UTCVendor advisory
  22. 2026-08-16 02:51 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-15 00:41 UTCVendor advisory
  26. 2026-08-15 00:41 UTCGHSA enrichment
  27. 2026-08-14 13:05 UTCVendor advisory
  28. 2026-08-14 13:05 UTCGHSA enrichment
  29. 2026-08-14 01:28 UTCEG score recompute
  30. 2026-08-14 01:28 UTCVendor advisory
  31. 2026-08-14 01:28 UTCGHSA enrichment
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 01:30 UTCVendor advisory
  34. 2026-08-13 01:30 UTCGHSA enrichment
  35. 2026-08-12 13:53 UTCEG score recompute
  36. 2026-08-12 13:53 UTCVendor advisory
  37. 2026-08-12 13:53 UTCGHSA enrichment
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-12 01:12 UTCEG score recompute
  40. 2026-08-12 01:12 UTCVendor advisory
  41. 2026-08-12 01:12 UTCGHSA enrichment
  42. 2026-08-11 13:35 UTCVendor advisory
  43. 2026-08-11 13:35 UTCGHSA enrichment
  44. 2026-08-11 00:13 UTCVendor advisory
  45. 2026-08-11 00:13 UTCGHSA enrichment
  46. 2026-08-10 08:18 UTCVendor advisory
  47. 2026-08-10 08:18 UTCGHSA enrichment
  48. 2026-08-09 20:42 UTCEG score recompute
  49. 2026-08-09 20:42 UTCVendor advisory
  50. 2026-08-09 20:42 UTCGHSA enrichment
  51. 2026-08-09 13:46 UTCEPSS rescore
  52. 2026-08-09 09:05 UTCVendor advisory
  53. 2026-08-09 09:05 UTCGHSA enrichment
  54. 2026-08-08 21:29 UTCEG score recompute
  55. 2026-08-08 21:29 UTCVendor advisory
  56. 2026-08-08 21:29 UTCGHSA enrichment
  57. 2026-08-08 16:37 UTCEPSS rescore
  58. 2026-08-08 06:58 UTCVendor advisory
  59. 2026-08-08 06:58 UTCGHSA enrichment
  60. 2026-08-07 19:22 UTCEG score recompute
  61. 2026-08-07 19:22 UTCVendor advisory
  62. 2026-08-07 19:22 UTCGHSA enrichment
  63. 2026-08-07 07:45 UTCVendor advisory
  64. 2026-08-07 07:45 UTCGHSA enrichment
  65. 2026-08-06 20:07 UTCEG score recompute
  66. 2026-08-06 20:07 UTCVendor advisory
  67. 2026-08-06 20:07 UTCGHSA enrichment
  68. 2026-08-06 13:47 UTCEPSS rescore
  69. 2026-08-06 08:30 UTCVendor advisory
  70. 2026-08-06 08:30 UTCGHSA enrichment
  71. 2026-08-05 20:54 UTCEG score recompute
  72. 2026-08-05 20:54 UTCVendor advisory
  73. 2026-08-05 20:54 UTCGHSA enrichment
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-04 10:39 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46045?
CVE-2026-46045 is a high vulnerability published on May 27, 2026. 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…
When was CVE-2026-46045 disclosed?
CVE-2026-46045 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46045 actively exploited?
CVE-2026-46045 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-46045?
CVE-2026-46045 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46045?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46045, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46045

Explore →

Is Your Infrastructure Affected by CVE-2026-46045?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.