# CVE-2025-68359: linux: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of qgroup record after fa... CVE-2025-68359 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2025-68359, released December 24, 2025. It is not reported as exploited. Patch Radar priority: Urgent. - Web page: https://patchblox.com/security/cve/CVE-2025-68359 - Priority: Urgent - CVSS: 9.8 (critical) - EPSS: 0.0063 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Dec 24, 2025 ## 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-azure sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.26.1.160000.2.7 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.26.1.160000.2.7 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.26.1 | [OPENSUSE-SU-2026:20287-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20287-1.md) | Feb 27, 2026 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.26.1 | [SUSE-SU-2026:20599-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20599-1.md) | Feb 27, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2025-68359](https://patchblox.com/security/data/fix/linux/debian-cve-2025-68359.md) | Dec 24, 2025 | | Linux | linux Debian 14 | 6.17.13-1 | [DEBIAN-CVE-2025-68359](https://patchblox.com/security/data/fix/linux/debian-cve-2025-68359.md) | Dec 24, 2025 | --- Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.