# btrfs: fix double free of qgroup record after failure to add delayed ref head

CVE record · `CVE-2025-68359`

- **Identifiers:** `CVE-2025-68359`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Dec 2025
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Dec 2025, 10:32 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.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `6ef8fbce010421bf742b12b8f8f2b2d2ff154845 to before 82d46660ebd94c269e3f25a77eb563621d8e67e3` (git)
  - affected: `6ef8fbce010421bf742b12b8f8f2b2d2ff154845 to before 7617680769e3119dfb3b43a2b7c287ce2242211c` (git)
  - affected: `6ef8fbce010421bf742b12b8f8f2b2d2ff154845 to before 364685c4c2d9c9f4408d95451bcf42fdeebc3ebb` (git)
  - affected: `6ef8fbce010421bf742b12b8f8f2b2d2ff154845 to before 725e46298876a2cc1f1c3fb22ba69d29102c3ddf` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.12`
  - unaffected: `before 6.12` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.17.13 to 6.17.*, inclusive` (semver)
  - unaffected: `6.18.2 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

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

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0063, the 50th percentile, on 18 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 24 Dec 2025. New records show when each source confirmed them.

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/82d46660ebd94c269e3f25a77eb563621d8e67e3>
- <https://git.kernel.org/stable/c/7617680769e3119dfb3b43a2b7c287ce2242211c>
- <https://git.kernel.org/stable/c/364685c4c2d9c9f4408d95451bcf42fdeebc3ebb>
- <https://git.kernel.org/stable/c/725e46298876a2cc1f1c3fb22ba69d29102c3ddf>

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

---

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