CPU hang via missing checkpoint-loop rescheduling
Published Sep 11, 2025 · Updated Sep 11, 2025
Denial of service in the Linux kernel jbd2 checkpoint path allows local users to hang a CPU during sustained ext4 writeback. The jbd2_log_do_checkpoint() loop releases and reacquires j_list_lock but lacks an explicit cond_resched() call, relying on flush or buffer waits that do not always sleep. Triggering requires low-privileged local access and prolonged checkpoint contention; the reported consequence is a soft lockup that stalls a CPU.
Summary
What happened
Denial of service in the Linux kernel jbd2 checkpoint path allows local users to hang a CPU during sustained ext4 writeback. The jbd2_log_do_checkpoint() loop releases and reacquires j_list_lock but lacks an explicit cond_resched() call, relying on flush or buffer waits that do not always sleep. Triggering requires low-privileged local access and prolonged checkpoint contention; the reported consequence is a soft lockup that stalls a CPU.
The record
- CVE
- CVE-2025-39782
- Published
- Sep 11, 2025
- Updated
- Sep 11, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-413, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 11, 2025CVE publishedPublication date reported by the CVE source.
- Sep 11, 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 <26cb9aad94cb1811d8fae115594cc71fa3d91ab0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3faac5e1d14c63260fd1bf789d96bde3ab3d9e54
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41f40038de62e8306897cf6840791b268996432a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <429d50cbaff45090d52a1ea850d5de8c14881ee7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <84ff98c1ea19acd3f9389e4bb6061364e943f85e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9d98cf4632258720f18265a058e62fde120c0151
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f683d611518d30334813eecf9a8c687453e2800e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f7ee8fd689e6d534f9fd2494b9266f7998082e65
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.
Public exploit references
No public exploit references are available in this record.
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