CVE-2026-46095

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (3)

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

md/md-llbitmap: raise barrier before state machine transition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef4ca3d4bf09716cff9ba00eb0351deadc8417ab
generic

md/md-llbitmap: raise barrier before state machine transition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9701d51dd378380ba05293fa391e8ba01065ae8d
generic

md/md-llbitmap: raise barrier before state machine transition - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9142f00a9287ca38152717e3e88a033a27774e7f

Vendor Advisories for CVE-2026-46095(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
linuxKernel @ 6.18.27—osv

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—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

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 206 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46095?
CVE-2026-46095 is a medium vulnerability published on May 27, 2026. 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 llbitmapstatemachine() in both llbitmapstartwrite() and llbitmapstartdiscard(). This ensures the barrier is in place…
When was CVE-2026-46095 disclosed?
CVE-2026-46095 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46095 actively exploited?
CVE-2026-46095 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-46095?
CVE-2026-46095 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46095?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46095, 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-46095

Explore →

Is Your Infrastructure Affected by CVE-2026-46095?

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

Start Free Scan →Browse All CVEs