CVE-2024-35949: btrfs: make sure that WRITTEN is set on all metadata blocks
btrfs: make sure that WRITTEN is set on all metadata blocks
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
Linux kernel btrfsto a version that resolves this vulnerability.Patch 732fab95abe2 - Configuration
Ensure the btrfs check-integrity code behavior matches the post-732fab95abe2 change: do not rely on CONFIG_BTRFS_FS_CHECK_INTEGRITY to call btrfs_check_leaf() during btrfs_mark_buffer_dirty(); instead, ensure the metadata leaf validation happens in __btrfs_check_leaf() regardless of call path.
btrfs CONFIG_BTRFS_FS_CHECK_INTEGRITY = removed (no longer call btrfs_check_leaf() from btrfs_mark_buffer_dirty())
Event History
Frequently Asked Questions
What is the severity of CVE-2024-35949?
CVE-2024-35949 has been classified with a moderate severity level due to its potential impact on data integrity.
How do I fix CVE-2024-35949?
To fix CVE-2024-35949, update your Linux kernel to version 6.12.12-1, 6.12.15-1 or later.
Which Linux kernel versions are affected by CVE-2024-35949?
CVE-2024-35949 affects Linux kernel versions up to 5.10.226-1 and 6.1.128-1.
Is there a workaround for CVE-2024-35949?
There is no known workaround for CVE-2024-35949, applying the update is the recommended action.
What components are impacted by CVE-2024-35949?
CVE-2024-35949 impacts the btrfs filesystem in the Linux kernel.