https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sun, 31 May 2026 16:36:10 +0000 https://vulnerability.circl.lu/sighting/b03608b9-e572-4283-8372-fff5daacc348/export {"uuid": "b03608b9-e572-4283-8372-fff5daacc348", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-49761", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/9361", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-49761\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: always report error in run_one_delayed_ref()\n\nCurrently we have a btrfs_debug() for run_one_delayed_ref() failure, but\nif end users hit such problem, there will be no chance that\nbtrfs_debug() is enabled. This can lead to very little useful info for\ndebugging.\n\nThis patch will:\n\n- Add extra info for error reporting\n Including:\n * logical bytenr\n * num_bytes\n * type\n * action\n * ref_mod\n\n- Replace the btrfs_debug() with btrfs_err()\n\n- Move the error reporting into run_one_delayed_ref()\n This is to avoid use-after-free, the @node can be freed in the caller.\n\nThis error should only be triggered at most once.\n\nAs if run_one_delayed_ref() failed, we trigger the error message, then\ncausing the call chain to error out:\n\nbtrfs_run_delayed_refs()\n`- btrfs_run_delayed_refs()\n `- btrfs_run_delayed_refs_for_head()\n `- run_one_delayed_ref()\n\nAnd we will abort the current transaction in btrfs_run_delayed_refs().\nIf we have to run delayed refs for the abort transaction,\nrun_one_delayed_ref() will just cleanup the refs and do nothing, thus no\nnew error messages would be output.\n\ud83d\udccf Published: 2025-03-27T16:43:07.633Z\n\ud83d\udccf Modified: 2025-03-28T15:21:57.235Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/18bd1c9c02e64a3567f90c83c2c8b855531c8098\n2. https://git.kernel.org/stable/c/fdb4a70bb768d2a87890409597529ad81cb3de8a\n3. https://git.kernel.org/stable/c/853ffa1511b058c79a4c9bb1407b3b20ce311792\n4. https://git.kernel.org/stable/c/39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92", "creation_timestamp": "2025-03-28T15:28:30.000000Z"} {"uuid": "b03608b9-e572-4283-8372-fff5daacc348", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-49761", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/9361", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2022-49761\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: always report error in run_one_delayed_ref()\n\nCurrently we have a btrfs_debug() for run_one_delayed_ref() failure, but\nif end users hit such problem, there will be no chance that\nbtrfs_debug() is enabled. This can lead to very little useful info for\ndebugging.\n\nThis patch will:\n\n- Add extra info for error reporting\n Including:\n * logical bytenr\n * num_bytes\n * type\n * action\n * ref_mod\n\n- Replace the btrfs_debug() with btrfs_err()\n\n- Move the error reporting into run_one_delayed_ref()\n This is to avoid use-after-free, the @node can be freed in the caller.\n\nThis error should only be triggered at most once.\n\nAs if run_one_delayed_ref() failed, we trigger the error message, then\ncausing the call chain to error out:\n\nbtrfs_run_delayed_refs()\n`- btrfs_run_delayed_refs()\n `- btrfs_run_delayed_refs_for_head()\n `- run_one_delayed_ref()\n\nAnd we will abort the current transaction in btrfs_run_delayed_refs().\nIf we have to run delayed refs for the abort transaction,\nrun_one_delayed_ref() will just cleanup the refs and do nothing, thus no\nnew error messages would be output.\n\ud83d\udccf Published: 2025-03-27T16:43:07.633Z\n\ud83d\udccf Modified: 2025-03-28T15:21:57.235Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/18bd1c9c02e64a3567f90c83c2c8b855531c8098\n2. https://git.kernel.org/stable/c/fdb4a70bb768d2a87890409597529ad81cb3de8a\n3. https://git.kernel.org/stable/c/853ffa1511b058c79a4c9bb1407b3b20ce311792\n4. https://git.kernel.org/stable/c/39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92", "creation_timestamp": "2025-03-28T15:28:30.000000Z"} https://vulnerability.circl.lu/sighting/b03608b9-e572-4283-8372-fff5daacc348/export Fri, 28 Mar 2025 15:28:30 +0000 https://vulnerability.circl.lu/sighting/2b7641ec-cf24-4c6c-b6bf-acf666ba5542/export {"uuid": "2b7641ec-cf24-4c6c-b6bf-acf666ba5542", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-49761", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "2b7641ec-cf24-4c6c-b6bf-acf666ba5542", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2022-49761", "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/2b7641ec-cf24-4c6c-b6bf-acf666ba5542/export Wed, 03 Dec 2025 14:14:49 +0000