# zram: fix potential UAF of zram table

CVE record · `CVE-2025-21671`

- **Identifiers:** `CVE-2025-21671`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 31 Jan 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 31 Jan 2025, 11:25 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: `ac3b5366b9b7c9d97b606532ceab43d2329a22f3 to before fe3de867f94819ba0f28e035c0b0182150147d95` (git)
  - affected: `0b5b0b65561b34e6e360de317e4bcd031bfabf42 to before 571d3f6045cd3a6d9f6aec33b678f3ffe97582ef` (git)
  - affected: `6fb92e9a52e3feae309a213950f21dfcd1eb0b40 to before 902ef8f16d5ca77edc77c30656be54186c1e99b7` (git)
  - affected: `74363ec674cb172d8856de25776c8f3103f05e2f to before 212fe1c0df4a150fb6298db2cfff267ceaba5402` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.1.122 to before 6.1.127` (semver)
  - affected: `6.6.68 to before 6.6.74` (semver)
  - affected: `6.12.7 to before 6.12.11` (semver)
  - Other versions: unaffected

## 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

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 31 Jan 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/fe3de867f94819ba0f28e035c0b0182150147d95>
- <https://git.kernel.org/stable/c/571d3f6045cd3a6d9f6aec33b678f3ffe97582ef>
- <https://git.kernel.org/stable/c/902ef8f16d5ca77edc77c30656be54186c1e99b7>
- <https://git.kernel.org/stable/c/212fe1c0df4a150fb6298db2cfff267ceaba5402>

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

---

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