# block: mark GFP_NOIO around sysfs ->store()

CVE record · `CVE-2025-21817`

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

Published by the CVE Program (CNA: Linux) at 27 Feb 2025, 20:04 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: `1645cd7fd42c236c952e9228badcac4fea1829ea to before a09280c39ea54080daf19cfaf4a3121a8d17d5cd` (git)
  - affected: `8985da5481562e96b95e94ed8e5cc9b6565eb82b to before 2566ce907e5d5db8a039647208e029ce559baa31` (git)
  - affected: `c99f66e4084a62a2cc401c4704a84328aeddc9ec to before 7c0be4ead1f8f5f8be0803f347de0de81e3b8e1c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.12.96 to before 6.12.109` (semver)
  - affected: `6.13.2 to before 6.13.3` (semver)
  - Other versions: unaffected

## Machine-written summary

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

> The Linux kernel block layer is affected in several version ranges, including 6.12.96 before 6.12.109 and 6.13.2 before 6.13.3, along with earlier commit-based ranges. The source describes a potential deadlock: sysfs store callbacks for the block queue allocate memory with GFP_KERNEL while the queue is frozen, which can trigger direct reclaim. The source does not say what an attacker could do, and it gives few details on exploitation. Upgrade to 6.12.109, 6.13.3, or a later fixed release. No workaround is listed.

Written 16 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.0015, the 4th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 27 Feb 2025, 20:04 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-21817)
- 27 Feb 2025, 20:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-21817)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/a09280c39ea54080daf19cfaf4a3121a8d17d5cd>
- <https://git.kernel.org/stable/c/2566ce907e5d5db8a039647208e029ce559baa31>
- <https://git.kernel.org/stable/c/7c0be4ead1f8f5f8be0803f347de0de81e3b8e1c>

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-2025-21817>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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