Kernel warning via sleep in atomic tracepoint
Published Jul 19, 2026 · Updated Jul 19, 2026
Improper context handling in Linux Kernel btrfs tracepoints allows local users to trigger a kernel warning during file synchronization. The btrfs_sync_file trace event calls dget_parent() and then dput() while executing in atomic context, where dput() can sleep. Triggering requires local access, an enabled btrfs_sync_file trace event, and btrfs file synchronization; published evidence demonstrates a kernel splat but not a crash.
Summary
What happened
Improper context handling in Linux Kernel btrfs tracepoints allows local users to trigger a kernel warning during file synchronization. The btrfs_sync_file trace event calls dget_parent() and then dput() while executing in atomic context, where dput() can sleep. Triggering requires local access, an enabled btrfs_sync_file trace event, and btrfs file synchronization; published evidence demonstrates a kernel splat but not a crash.
The record
- CVE
- CVE-2026-64164
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record 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=2e4adfaec97ee053ad1bdfb5036845e66f7e0d8a <c32a7e0e3c73c1c0768556a56bd78de9f7b83780
- Affected versionversion=32372781d664a9b03c40343e96c29d0a6139f97d <12a0487945c09760a5968d9333383014ea294117
- Affected versionversion=4a7bab35fad5251c8cb738161152578cd83b6b9c <d78b0a80eac36879ef5478707135c446920e134b
- Affected versionversion=520e8b4bcf872a534a7bf61ccf880047642df296 <4361954f0e158af0530caa1e57f12b531be4658f
- Affected versionversion=6.12.83 <6.12.92
- Affected versionversion=6.18.24 <6.18.34
- Affected versionversion=6.19.14 <6.20
- Affected versionversion=6.6.136 <6.6.142
- Affected versionversion=7.0
- Affected versionversion=a85b46db143fda5869e7d8df8f258ccef5fa1719 <0a96d9a85cd2240481297156b9bb72e10b7a8036
- Affected versionversion=a85b46db143fda5869e7d8df8f258ccef5fa1719 <c73370c677646e86fc4b1780fb07027bdf847375
- Affected versionversion=c09a7446aab5773f38d6abb25fce99b8e1dfbc97 <26b2290baaf6da6add0f782a100766e686a33f4f
- Affected versionversion=d110d7cdb045715c0b45b0dfd974525bb38f653d
- Affected versionversion=e252db8ca2a01f82d472091f35d549b313278636 <6279992c9ba2774901c9d4dd4a481162e2534714
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
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