Kernel crash via stale reappeared-device state
Published Aug 6, 2026 · Updated Aug 6, 2026
A NULL pointer dereference in affected Linux Btrfs kernels allows local users with administrative storage access to crash the kernel via FITRIM. device_list_add() clears the missing-device flag after a device reappears but leaves its block-device pointer null; btrfs_trim_free_extents_throttle() then dereferences it during discard sizing. Triggering requires a degraded multi-device Btrfs filesystem, device rescanning, and a privileged FITRIM operation; the reported consequence is a kernel crash.
Summary
What happened
A NULL pointer dereference in affected Linux Btrfs kernels allows local users with administrative storage access to crash the kernel via FITRIM. device_list_add() clears the missing-device flag after a device reappears but leaves its block-device pointer null; btrfs_trim_free_extents_throttle() then dereferences it during discard sizing. Triggering requires a degraded multi-device Btrfs filesystem, device rescanning, and a privileged FITRIM operation; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2026-64593
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=4.3
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <02c903fc6fc7e16c5d1f22d18784f1208acf43e3
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <1b1937eb08f51319bf71575484cde2b8c517aedc
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <210af872eafa0cf572a84cb303c0f9d2914c1226
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <3d8fa4b828a86b33c60858e58aaab6df273ede05
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <7a64521802997257b144e6edfb4e278dbeb972dd
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <9c894159c5b8adc84072e3af0e55b0473a69564e
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <b4af31b898a948e29861cb0bae734058f9a49d9b
- Affected versionversion=499f377f49f085ee4aa214c738e948e88626f39b <f41ae7e6664f3c4361129728f2c4d5f3ed995251
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