CVE-2023-52668

What it actually does

Incorrect ordering of zone_active_bgs_lock and per-block_group cache lock in btrfs_zone_activate creates a potential circular dependency that can deadlock the kernel on zoned Btrfs volumes.

Why it matters to the business

Workloads using Btrfs on zoned storage may experience sudden system hangs or forced reboots, increasing downtime and risking data inconsistency during recovery.

How an attack unfolds

An attacker with local access triggers concurrent zoned block-group activation and background finish operations so that the two locks are acquired in opposite order from the documented sequence, causing the kernel to stall.

How to fix it

Upgrade the Linux kernel to a version containing commit 6f74989f5909cdec9b1274641f0fa306b15bb476 or later; rebuild and reboot with the fixed kernel.

How to confirm the fix worked

Boot the updated kernel, run generic/129 or equivalent zoned Btrfs stress tests, and confirm no lockdep warnings appear in dmesg referencing zone_active_bgs_lock or cache lock.

Typical attack path

1. Mount a Btrfs filesystem on a zoned device
2. Trigger zone activation via write or balance activity
3. Induce concurrent block-group finishing that acquires locks in reverse order
4. Kernel thread deadlocks waiting on the inverted locks

How to detect it

Search kernel logs and dmesg for lockdep warnings that mention zone_active_bgs_lock followed by cache lock or btrfs_zone_finish_one_bg.

What your security team should do

• Prioritize kernel updates on all systems using Btrfs with zoned storage
• Add lockdep-enabled kernel builds to CI for Btrfs zoned tests
• Monitor dmesg for circular-locking warnings on production zoned hosts