https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Fri, 05 Jun 2026 21:59:25 +0000 https://vulnerability.circl.lu/sighting/89556c4a-85bf-4f89-a5a5-bf3d219b9ff2/export {"uuid": "89556c4a-85bf-4f89-a5a5-bf3d219b9ff2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} {"uuid": "89556c4a-85bf-4f89-a5a5-bf3d219b9ff2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"} https://vulnerability.circl.lu/sighting/89556c4a-85bf-4f89-a5a5-bf3d219b9ff2/export Wed, 04 Sep 2024 21:57:06 +0000 https://vulnerability.circl.lu/sighting/650f9da1-40a2-429c-9a5b-03a2de6df926/export {"uuid": "650f9da1-40a2-429c-9a5b-03a2de6df926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44963", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "650f9da1-40a2-429c-9a5b-03a2de6df926", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-44963", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://vulnerability.circl.lu/sighting/650f9da1-40a2-429c-9a5b-03a2de6df926/export Wed, 03 Dec 2025 14:14:49 +0000 https://vulnerability.circl.lu/sighting/097ae0a5-382e-41b5-aaba-5d2ce8adb75b/export {"uuid": "097ae0a5-382e-41b5-aaba-5d2ce8adb75b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-44963", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "097ae0a5-382e-41b5-aaba-5d2ce8adb75b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-44963", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://vulnerability.circl.lu/sighting/097ae0a5-382e-41b5-aaba-5d2ce8adb75b/export Thu, 19 Mar 2026 00:00:00 +0000