CVE-2024-46687: btrfs: fix a use-after-free when hitting errors inside btrfs_submit_chunk()
btrfs: fix a use-after-free when hitting errors inside btrfssubmitchunk()
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Configuration
Apply the btrfs fix: in the error path inside btrfs_submit_chunk(), replace calls to btrfs_bio_end_io() with btrfs_orig_bbio_end_io(), which has an extra check on split bios to prevent a slab use-after-free/double free.
Linux kernel btrfs btrfs_submit_chunk() endio handling = call btrfs_orig_bbio_end_io() instead of btrfs_bio_end_io()
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46687?
CVE-2024-46687 has been classified as a medium severity vulnerability due to its impact on memory safety.
How do I fix CVE-2024-46687?
To remediate CVE-2024-46687, ensure your Linux kernel is updated to a version that includes the fix, such as patches from version 6.6.50 or above.
What systems are affected by CVE-2024-46687?
CVE-2024-46687 affects various versions of the Linux kernel, specifically those between 6.3 and 6.6.49, along with several release candidates of version 6.11.
What does CVE-2024-46687 entail?
CVE-2024-46687 involves a use-after-free situation in the btrfs file system, which can lead to potential security issues if not addressed.
Is there a public exploit for CVE-2024-46687?
As of now, there are no known public exploits for CVE-2024-46687, though the vulnerability should still be promptly patched.