Kernel panic via Btrfs balance-control race
Published Sep 17, 2025 · Updated Sep 17, 2025
Race condition in Btrfs in Linux 6.1.42 through 6.1.46 and 6.4.7 through 6.4.11 allows local users to panic the kernel via ioctls. After balance_mutex is dropped and reacquired, btrfs_cancel_balance evaluates a BUG_ON assertion without accounting for a concurrent pause request during cancellation. Reachability requires a local user able to issue concurrent Btrfs balance pause and cancel ioctls, and successful exploitation crashes the host without other reported side effects.
Summary
What happened
Race condition in Btrfs in Linux 6.1.42 through 6.1.46 and 6.4.7 through 6.4.11 allows local users to panic the kernel via ioctls. After balance_mutex is dropped and reacquired, btrfs_cancel_balance evaluates a BUG_ON assertion without accounting for a concurrent pause request during cancellation. Reachability requires a local user able to issue concurrent Btrfs balance pause and cancel ioctls, and successful exploitation crashes the host without other reported side effects.
The record
- CVE
- CVE-2023-53339
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29eefa6d0d07e185f7bfe9576f91e6dba98189c2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c93b89cd46636b5e74c12fa21dd86167bc6ea8d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a0a462a0f20926918d6009f0b4b25673e883fc98
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae81329f7de3aa6f34ecdfa5412e72161a30e9ce
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b966e9e1e250dfdb41a7f41775faea4a37af923c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd7bef82ce0e929ef4cf63a34990545aaca28077
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ceb9ba8e30833a4823e2dc73f80ebcdf2498d01a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- syzbot Btrfs balance-cancellation reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo