https://vulnerability.circl.lu/sightings/feed 2026-05-10T05:03:28.768951+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/c9309f20-9968-4497-864a-fcfb92cc7fb8/export 2026-05-10T05:03:29.137951+00:00 Automation user http://cve.circl.lu/user/automation {"uuid": "c9309f20-9968-4497-864a-fcfb92cc7fb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52897", "type": "seen", "source": "https://t.me/cvedetector/3744", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-52897 - btrfs GOOS BUG\", \n \"Content\": \"CVE ID : CVE-2023-52897 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nbtrfs: qgroup: do not warn on record without old_roots populated \n \n[BUG] \nThere are some reports from the mailing list that since v6.1 kernel, the \nWARN_ON() inside btrfs_qgroup_account_extent() gets triggered during \nrescan: \n \n WARNING: CPU: 3 PID: 6424 at fs/btrfs/qgroup.c:2756 btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] \n CPU: 3 PID: 6424 Comm: snapperd Tainted: P OE 6.1.2-1-default #1 openSUSE Tumbleweed 05c7a1b1b61d5627475528f71f50444637b5aad7 \n RIP: 0010:btrfs_qgroup_account_extents+0x1ae/0x260 [btrfs] \n Call Trace: \n \n btrfs_commit_transaction+0x30c/0xb40 [btrfs c39c9c546c241c593f03bd6d5f39ea1b676250f6] \n ? start_transaction+0xc3/0x5b0 [btrfs c39c9c546c241c593f03bd6d5f39ea1b676250f6] \n btrfs_qgroup_rescan+0x42/0xc0 [btrfs c39c9c546c241c593f03bd6d5f39ea1b676250f6] \n btrfs_ioctl+0x1ab9/0x25c0 [btrfs c39c9c546c241c593f03bd6d5f39ea1b676250f6] \n ? __rseq_handle_notify_resume+0xa9/0x4a0 \n ? mntput_no_expire+0x4a/0x240 \n ? __seccomp_filter+0x319/0x4d0 \n __x64_sys_ioctl+0x90/0xd0 \n do_syscall_64+0x5b/0x80 \n ? syscall_exit_to_user_mode+0x17/0x40 \n ? do_syscall_64+0x67/0x80 \n entry_SYSCALL_64_after_hwframe+0x63/0xcd \n RIP: 0033:0x7fd9b790d9bf \n \n \n[CAUSE] \nSince commit e15e9f43c7ca (\"btrfs: introduce \nBTRFS_QGROUP_RUNTIME_FLAG_NO_ACCOUNTING to skip qgroup accounting\"), if \nour qgroup is already in inconsistent state, we will no longer do the \ntime-consuming backref walk. \n \nThis can leave some qgroup records without a valid old_roots ulist. \nNormally this is fine, as btrfs_qgroup_account_extents() would also skip \nthose records if we have NO_ACCOUNTING flag set. \n \nBut there is a small window, if we have NO_ACCOUNTING flag set, and \ninserted some qgroup_record without a old_roots ulist, but then the user \ntriggered a qgroup rescan. \n \nDuring btrfs_qgroup_rescan(), we firstly clear NO_ACCOUNTING flag, then \ncommit current transaction. \n \nAnd since we have a qgroup_record with old_roots = NULL, we trigger the \nWARN_ON() during btrfs_qgroup_account_extents(). \n \n[FIX] \nUnfortunately due to the introduction of NO_ACCOUNTING flag, the \nassumption that every qgroup_record would have its old_roots populated \nis no longer correct. \n \nFix the false alerts and drop the WARN_ON(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:07.000000Z"} 2024-08-21T09:52:07+00:00