CVE-2025-68359btrfs: fix double free of qgroup record after failure to add delayed ref head
- 9.8CriticalCVSS base score
- 0.63%Exploitation in 30 daysEPSS · top 50% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of qgroup record after failure to add delayed ref head In the previous code it was possible to incur into a double kfree() scenario when calling add_delayed_ref_head(). This could happen if the record was reported to already exist in the btrfs_qgroup_trace_extent_nolock() call, but then there was an error later on add_delayed_ref_head(). In this case, since add_delayed_ref_head() returned an error, the caller went to free the record. Since add_delayed_ref_head() couldn't set this kfree'd pointer to NULL, then kfree() would have acted on a non-NULL 'record' object which was pointing to memory already freed by the callee. The problem comes from the fact that the responsibility to kfree the object is on both the caller and the callee at the same time. Hence, the fix for this is to shift the ownership of the 'qrecord' object out of the add_delayed_ref_head(). That is, we will never attempt to kfree() the given object inside of this function, and will expect the caller to act on the 'qrecord' object on its own. The only exception where the 'qrecord' object cannot be kfree'd is if it was inserted into the tracing logic, for which we already have the 'qrecord_inserted_ret' boolean to account for this. Hence, the caller has to kfree the object only if add_delayed_ref_head() reports not to have inserted it on the tracing logic. As a side-effect of the above, we must guarantee that 'qrecord_inserted_ret' is properly initialized at the start of the function, not at the end, and then set when an actual insert happens. This way we avoid 'qrecord_inserted_ret' having an invalid value on an early exit. The documentation from the add_delayed_ref_head() has also been updated to reflect on the exact ownership of the 'qrecord' object.
Timeline
ID reserved
By Linux
- 8 days later
· 8 days later
Published
- 10 months later
· 10 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.63% · top 50% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 6ef8fbce010421bf742b12b8f8f2b2d2ff154845 – < 82d46660ebd94c269e3f25a77eb563621d8e67e3
- affected 6ef8fbce010421bf742b12b8f8f2b2d2ff154845 – < 7617680769e3119dfb3b43a2b7c287ce2242211c
- affected 6ef8fbce010421bf742b12b8f8f2b2d2ff154845 – < 364685c4c2d9c9f4408d95451bcf42fdeebc3ebb
- affected 6ef8fbce010421bf742b12b8f8f2b2d2ff154845 – < 725e46298876a2cc1f1c3fb22ba69d29102c3ddf
- affected 6.12
- unaffected < 6.12
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.17.13 – ≤ 6.17.*
- unaffected 6.18.2 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References4
- https://git.kernel.org/stable/c/82d46660ebd94c269e3f25a77eb563621d8e67e3 (opens in a new tab)
- https://git.kernel.org/stable/c/7617680769e3119dfb3b43a2b7c287ce2242211c (opens in a new tab)
- https://git.kernel.org/stable/c/364685c4c2d9c9f4408d95451bcf42fdeebc3ebb (opens in a new tab)
- https://git.kernel.org/stable/c/725e46298876a2cc1f1c3fb22ba69d29102c3ddf (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-205095 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68359)Record last updated .