Local kernel code execution via writeback race
Published Sep 19, 2025 · Updated Sep 19, 2025
Use-after-free in Linux kernel writeback allows local users to execute kernel code via concurrent inode writes and cgroup switching. __mark_inode_dirty() releases inode->i_lock before wb_wakeup_delayed() finishes, allowing inode_switch_wbs_work_fn() to free the old bdi_writeback before it is dereferenced. An unprivileged local account with file-write access and delegated cgroup activity can trigger the race, causing kernel-memory disclosure, kernel code execution, or a panic.
Summary
What happened
Use-after-free in Linux kernel writeback allows local users to execute kernel code via concurrent inode writes and cgroup switching. __mark_inode_dirty() releases inode->i_lock before wb_wakeup_delayed() finishes, allowing inode_switch_wbs_work_fn() to free the old bdi_writeback before it is dereferenced. An unprivileged local account with file-write access and delegated cgroup activity can trigger the race, causing kernel-memory disclosure, kernel code execution, or a panic.
The record
- CVE
- CVE-2025-39866
- Published
- Sep 19, 2025
- Updated
- Sep 19, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 19, 2025CVE publishedPublication date reported by the CVE source.
- Sep 19, 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 <1edc2feb9c759a9883dfe81cb5ed231412d8b2e4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b187c976111960e6e54a6b1fff724f6e3d39406c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bf89b1f87c72df79cf76203f71fbf8349cd5c9de
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8c14adf80bd1a6e4a1d7ee9c2a816881c26d17a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d02d2c98d25793902f65803ab853b592c7a96b29
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e63052921f1b25a836feb1500b841bff7a4a0456
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
- byteReaper77 CVE-2025-39866 proof of conceptproof of concept · unverified
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