CVE-2026-46095

NONECVSS 0.0

0.0

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: —
EG Score: 0.0(none)
EPSS: 4.3%
KEV: Not listed

Published

May 27, 2026

Last Modified

May 27, 2026

References (3)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9142f00a9287ca38152717e3e88a033a27774e7f
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9701d51dd378380ba05293fa391e8ba01065ae8d
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ef4ca3d4bf09716cff9ba00eb0351deadc8417ab

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.

GHSA-qghx-f73p-v22r
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: md/md-llbitmap: raise...

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 14:07 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-46095?

CVE-2026-46095 is a none 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. 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 4.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

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

CVE-2026-46095

📅 Published

🔄 Last Modified

🔗 References (3)

📣 Vendor Advisories for CVE-2026-46095(1)