{"uuid": "89556c4a-85bf-4f89-a5a5-bf3d219b9ff2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44963", "type": "seen", "source": "https://t.me/cvedetector/4850", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44963 - \"Btrfs Memory Leak BUG Abuse Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-44963 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: do not BUG_ON() when freeing tree block after error  \n  \nWhen freeing a tree block, at btrfs_free_tree_block(), if we fail to  \ncreate a delayed reference we don't deal with the error and just do a  \nBUG_ON(). The error most likely to happen is -ENOMEM, and we have a  \ncomment mentioning that only -ENOMEM can happen, but that is not true,  \nbecause in case qgroups are enabled any error returned from  \nbtrfs_qgroup_trace_extent_post() (can be -EUCLEAN or anything returned  \nfrom btrfs_search_slot() for example) can be propagated back to  \nbtrfs_free_tree_block().  \n  \nSo stop doing a BUG_ON() and return the error to the callers and make  \nthem abort the transaction to prevent leaking space. Syzbot was  \ntriggering this, likely due to memory allocation failure injection. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:57:06.000000Z"}