# md/raid5: fix IO hang with degraded array with llbitmap

CVE record · `CVE-2026-45953`

- **Identifiers:** `CVE-2026-45953`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 May 2026, 12:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `5ab829f1971dc99f2aac10846c378e67fc875abc to before 870b9f15867b0e70f3459ef3974b043e8b229690` (git)
  - affected: `5ab829f1971dc99f2aac10846c378e67fc875abc to before 28ef299e7a5b81817f8ca8297c2ddff28f5da5e8` (git)
  - affected: `5ab829f1971dc99f2aac10846c378e67fc875abc to before cd1635d844d26471c56c0a432abdee12fc9ad735` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.18`
  - unaffected: `before 6.18` (semver)
  - unaffected: `6.18.14 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.4 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions from commit 5ab829f1971d up to the listed fixes are affected, including 6.18 and earlier releases in that range. The flaw is in the md/raid5 driver for degraded RAID arrays using llbitmap: a write-handling check is missing, so stripe processing can loop without progress, causing an IO hang. The source gives few details about how an attacker would trigger this. Upgrade to a fixed kernel: 6.18.14 or later in the 6.18 series, 6.19.4 or later in the 6.19 series, or 7.0 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 May 2026, 12:18 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-45953)
- 27 May 2026, 14:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-45953)

## Sources

- [CVE List: CVE-2026-45953](https://www.cve.org/CVERecord?id=CVE-2026-45953)
- [NVD: CVE-2026-45953](https://nvd.nist.gov/vuln/detail/CVE-2026-45953)

### References from the CNA

- <https://git.kernel.org/stable/c/870b9f15867b0e70f3459ef3974b043e8b229690>
- <https://git.kernel.org/stable/c/28ef299e7a5b81817f8ca8297c2ddff28f5da5e8>
- <https://git.kernel.org/stable/c/cd1635d844d26471c56c0a432abdee12fc9ad735>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-45953>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-45953/>. Everything for agents: <https://agentprime.io/llms.txt>.
