DEBIAN-CVE-2025-68359

See a problem?
Please try reporting it to the source first.

Source

https://security-tracker.debian.org/tracker/CVE-2025-68359

Import Source

https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-68359.json

JSON Data

https://api.osv.dev/v1/vulns/DEBIAN-CVE-2025-68359

Upstream

CVE-2025-68359

Published

2025-12-24T11:15:59Z

Modified

2026-09-01T20:05:57Z

Severity

9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator

Summary

[none]

Details

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.

References

https://security-tracker.debian.org/tracker/CVE-2025-68359

Affected packages

Debian:13 / linux

Package

Name: linux
Purl: pkg:deb/debian/linux?arch=source&distro=trixie

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0 Unknown introduced version / All previous versions are affected

Affected versions

6.*

6.12.38-1

6.12.41-1

6.12.43-1~bpo12+1

6.12.43-1

6.12.48-1

6.12.57-1~bpo12+1

6.12.57-1

6.12.63-1~bpo12+1

6.12.63-1

6.12.69-1~bpo12+1

6.12.69-1

6.12.73-1~bpo12+1

6.12.73-1

6.12.74-1

6.12.74-2~bpo12+1

6.12.74-2

6.12.85-1~bpo12+1

6.12.85-1

6.12.86-1~bpo12+1

6.12.86-1

6.12.88-1~bpo12+1

6.12.88-1

6.12.90-1~bpo12+1

6.12.90-1

6.12.90-2~bpo12+1

6.12.90-2

6.12.94-1~bpo12+1

6.12.94-1

6.12.95-1~bpo12+1

6.12.95-1

6.12.96-1

6.12.100-1

6.12.101-1

6.12.105-1

6.12.107-1

6.13~rc6-1~exp1

6.13~rc7-1~exp1

6.13.2-1~exp1

6.13.3-1~exp1

6.13.4-1~exp1

6.13.5-1~exp1

6.13.6-1~exp1

6.13.7-1~exp1

6.13.8-1~exp1

6.13.9-1~exp1

6.13.10-1~exp1

6.13.11-1~exp1

6.14.3-1~exp1

6.14.5-1~exp1

6.14.6-1~exp1

6.15~rc7-1~exp1

6.15-1~exp1

6.15.1-1~exp1

6.15.2-1~exp1

6.15.3-1~exp1

6.15.4-1~exp1

6.15.5-1~exp1

6.15.6-1~exp1

6.16~rc7-1~exp1

6.16-1~exp1

6.16.1-1~exp1

6.16.3-1~bpo13+1

6.16.3-1

6.16.5-1

6.16.6-1

6.16.7-1

6.16.8-1

6.16.9-1

6.16.10-1

6.16.11-1

6.16.12-1~bpo13+1

6.16.12-1

6.16.12-2

6.17.2-1~exp1

6.17.5-1~exp1

6.17.6-1

6.17.7-1

6.17.7-2

6.17.8-1~bpo13+1

6.17.8-1

6.17.9-1

6.17.10-1

6.17.11-1

6.17.12-1

6.17.13-1~bpo13+1

6.17.13-1

6.18~rc4-1~exp1

6.18~rc4-1~exp2

6.18~rc5-1~exp1

6.18~rc6-1~exp1

6.18~rc7-1~exp1

6.18.1-1~exp1

6.18.2-1~exp1

6.18.3-1

6.18.5-1~bpo13+1

6.18.5-1

6.18.8-1

6.18.9-1~bpo13+1

6.18.9-1

6.18.10-1

6.18.12-1~bpo13+1

6.18.12-1

6.18.13-1

6.18.14-1

6.18.15-1~bpo13+1

6.18.15-1

6.19~rc4-1~exp1

6.19~rc5-1~exp1

6.19~rc6-1~exp1

6.19~rc7-1~exp1

6.19~rc8-1~exp1

6.19-1~exp1

6.19.2-1~exp1

6.19.3-1~exp1

6.19.4-1~exp1

6.19.5-1~exp1

6.19.6-1

6.19.6-2~bpo13+1

6.19.6-2

6.19.8-1~bpo13+1

6.19.8-1

6.19.10-1~bpo13+1

6.19.10-1

6.19.11-1~bpo13+1

6.19.11-1

6.19.12-1

6.19.13-1~bpo13+1

6.19.13-1

6.19.14-1~bpo13+1

6.19.14-1

7.*

7.0-1~exp1

7.0.1-1~exp1

7.0.3-1

7.0.4-1~bpo13+1

7.0.4-1

7.0.7-1~bpo13+1

7.0.7-1

7.0.9-1~bpo13+1

7.0.9-1

7.0.10-1~bpo13+1

7.0.10-1

7.0.12-1

7.0.12-2~bpo13+1

7.0.12-2

7.0.13-1~bpo13+1

7.0.13-1

7.0.14-1

7.1~rc2-1~exp1

7.1~rc3-1~exp1

7.1~rc4-1~exp1

7.1~rc4-1~exp2

7.1~rc5-1~exp1

7.1~rc7-1~exp1

7.1.1-1~exp1

7.1.2-1~exp1

7.1.3-1~bpo13+1

7.1.3-1

7.1.3-1+sunvdc

7.1.4-1

7.1.5-1

7.1.6-1

7.1.7-1~bpo13+1

7.1.7-1

7.1.8-1~bpo13+1

7.1.8-1

7.1.8-2

7.1.9-1

7.1.9-1+sparc64

7.1.10-1

7.1.12-1

7.2~rc3-1~exp1

7.2~rc5-1~exp1

7.2~rc7-1~exp1

7.2.2-1~exp1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Database specific

source

"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-68359.json"

Debian:14 / linux