cve.bz

CVE-2025-68359 linux linux

9.8 criticalEPSS 0.6%Fix available

Critical (9.8) in linux linux. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.17.13
  • Linux Linux: fixed in 6.18.2
  • Linux Linux: fixed in 6.19
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-68359 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68359?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68359?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68359 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68359

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68359](https://cve.bz/cve/badge/CVE-2025-68359.svg)](https://cve.bz/cve/CVE-2025-68359)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68359"><img src="https://cve.bz/cve/badge/CVE-2025-68359.svg" alt="CVE-2025-68359"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.12 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.114
Linux6.176.17.13
Linux6.186.18.2
Linuxlater releases6.19

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2025-68359
Debian13linux6.12.115-2DEBIAN-CVE-2025-68359
Debian14linux6.17.13-1DEBIAN-CVE-2025-68359
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68359
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68359
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68359
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68359
Ubuntu24.04:LTSlinux-aws-6.176.17.0-1009.9~24.04.2UBUNTU-CVE-2025-68359 USN-8094-1
Ubuntu24.04:LTSlinux-azure-6.176.17.0-1010.10~24.04.1UBUNTU-CVE-2025-68359 USN-8094-4
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1009.9~24.04.3UBUNTU-CVE-2025-68359 USN-8094-2
Ubuntu24.04:LTSlinux-hwe-6.176.17.0-19.19~24.04.2UBUNTU-CVE-2025-68359 USN-8094-1
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68359
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1017.17UBUNTU-CVE-2025-68359 USN-8152-1
Ubuntu24.04:LTSlinux-oracle-6.176.17.0-1009.9~24.04.1UBUNTU-CVE-2025-68359 USN-8094-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 16 moreno fix listedUBUNTU-CVE-2025-68359
9 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.26.1SUSE-SU-2026:20615-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.26.1SUSE-SU-2026:20599-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.26.1.160000.2.7SUSE-SU-2026:20599-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.26.1.160000.2.7SUSE-SU-2026:20555-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.26.1SUSE-SU-2026:20555-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.26.1SUSE-SU-2026:20570-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.26.1.160000.2.7openSUSE-SU-2026:20287-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.26.1openSUSE-SU-2026:20287-1
openSUSETumbleweedkernel-source6.18.5-1.1openSUSE-SU-2026:10039-1
openSUSETumbleweedkernel-source-longterm6.18.16-1.1openSUSE-SU-2026:10301-1
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2025-68359
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68359

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low-severity flaw was found in the Linux kernel's btrfs file system implementation. When quota groups (qgroups) are enabled on a btrfs file system, ownership of a heap-allocated qgroup trace record was ambiguously shared between add_delayed_ref_head() and its caller. If btrfs_qgroup_trace_extent_nolock() reported that a record already existed and add_delayed_ref_head() subsequently failed, the callee could free the record while the caller still held a non-NULL pointer, causing a double kfree() on the error path. A local user with access to a mounted btrfs file system with qgroups enabled could trigger this condition through filesystem operations that generate delayed references, most likely resulting in memory corruption or a kernel crash (denial of service). The vulnerable code is not present in the Red Hat Enterprise Linux 7, 8, 9, and 10 kernel and kernel-rt packages nor in the Red Hat In-Vehicle OS 1 kernel, so those products are not affected; the only Red Hat entry marked as affected is the Red Hat Enterprise Linux 6 Extended Lifecycle Support kernel, which is out of support scope. The upstream CVEORG severity of Critical (CVSS 9.8, network attack vector) does not reflect the actual risk: exploitation requires local access to a system with a mounted btrfs file system with quota groups enabled and depends on a narrow error path, with availability being the primary impact. For these reasons Red Hat rates this flaw LOW with a CVSS of 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68359.

References

Check your stackJSON