In the Linux kernel, the following vulnerability has been resolved: btrfs: do not trim a device which is not writeable [BUG] There is a bug report… (CVE-2026-64593)
A vulnerability in the Linux kernel's Btrfs filesystem code could cause a NULL pointer dereference when trimming a device that is not writable. This occurs due to a race condition where a missing device is re-scanned and its missing flag cleared without properly updating its writable state or device pointer, leading to a kernel crash. The issue has been identified and resolved in the Linux kernel.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-64593) involves the Btrfs filesystem in the Linux kernel where the function btrfs_trim_fs() may attempt to trim a device that is not writable, resulting in a NULL pointer dereference. This happens because the device's bdev pointer remains NULL after the device re-appears and the BTRFS_DEV_STATE_MISSING flag is cleared, but the BTRFS_DEV_STATE_WRITEABLE flag is not set. The kernel then crashes when btrfs_trim_free_extents_throttle() calls bdev_max_discard_sectors() on a NULL pointer. The root cause is a desynchronization between the device state flags and the device pointer during device re-scanning. A fix has been implemented to address this gap in handling re-appearing devices.
Potential Impact
This vulnerability can cause a kernel NULL pointer dereference leading to a system crash (kernel panic) when the Btrfs filesystem attempts to trim a device that is not writable. This results in denial of service due to the kernel crash. There is no indication of privilege escalation or data corruption beyond the crash.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should update to the fixed kernel version once available. Since this is a kernel-level issue, applying the official kernel patch or upgrading to a kernel version that includes the fix is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel mailing lists for the exact fixed version and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: btrfs: do not trim a device which is not writeable [BUG] There is a bug report… (CVE-2026-64593)
Description
A vulnerability in the Linux kernel's Btrfs filesystem code could cause a NULL pointer dereference when trimming a device that is not writable. This occurs due to a race condition where a missing device is re-scanned and its missing flag cleared without properly updating its writable state or device pointer, leading to a kernel crash. The issue has been identified and resolved in the Linux kernel.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-64593) involves the Btrfs filesystem in the Linux kernel where the function btrfs_trim_fs() may attempt to trim a device that is not writable, resulting in a NULL pointer dereference. This happens because the device's bdev pointer remains NULL after the device re-appears and the BTRFS_DEV_STATE_MISSING flag is cleared, but the BTRFS_DEV_STATE_WRITEABLE flag is not set. The kernel then crashes when btrfs_trim_free_extents_throttle() calls bdev_max_discard_sectors() on a NULL pointer. The root cause is a desynchronization between the device state flags and the device pointer during device re-scanning. A fix has been implemented to address this gap in handling re-appearing devices.
Potential Impact
This vulnerability can cause a kernel NULL pointer dereference leading to a system crash (kernel panic) when the Btrfs filesystem attempts to trim a device that is not writable. This results in denial of service due to the kernel crash. There is no indication of privilege escalation or data corruption beyond the crash.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel. Users should update to the fixed kernel version once available. Since this is a kernel-level issue, applying the official kernel patch or upgrading to a kernel version that includes the fix is the recommended remediation. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel mailing lists for the exact fixed version and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2hc3-vpvv-mwv3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64593"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cfa0bf8831d5391b07a6
Added to database: 08/06/2026, 18:17:04 UTC
Last enriched: 08/06/2026, 19:12:48 UTC
Last updated: 08/07/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.