DEBIAN-CVE-2023-52668
- Source
- https://security-tracker.debian.org/tracker/CVE-2023-52668
- Import Source
- https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-52668.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2023-52668
- Upstream
- Published
- 2024-05-17T14:15:09Z
- Modified
- 2025-09-25T22:40:39Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix lock ordering in btrfszoneactivate() The btrfs CI reported a lockdep warning as follows by running generic generic/129. WARNING: possible circular locking dependency detected 6.7.0-rc5+ #1 Not tainted ------------------------------------------------------ kworker/u5:5/793427 is trying to acquire lock: ffff88813256d028 (&cache->lock){+.+.}-{2:2}, at: btrfszonefinishonebg+0x5e/0x130 but task is already holding lock: ffff88810a23a318 (&fsinfo->zoneactivebgslock){+.+.}-{2:2}, at: btrfszonefinishonebg+0x34/0x130 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&fsinfo->zoneactivebgslock){+.+.}-{2:2}: ... -> #0 (&cache->lock){+.+.}-{2:2}: ... This is because we take fsinfo->zoneactivebgslock after a blockgroup's lock in btrfszoneactivate() while doing the opposite in other places. Fix the issue by expanding the fsinfo->zoneactivebgslock's critical section and taking it before a blockgroup's lock.
- References
Affected packages
Debian:13 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source
Debian:14 / linux
Package
- Name
- linux
- Purl
- pkg:deb/debian/linux?arch=source