{"vulnerability": "CVE-2024-49854", "sightings": [{"uuid": "160825bc-75a1-476c-bad7-60f03dbaed0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-49854", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "ba51ae6d-4589-42df-b355-19336d1005e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49854", "type": "seen", "source": "https://t.me/cvedetector/8484", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-49854 - Linux Kernel BlockBFQ Uninitialized Function Pointer\", \n  \"Content\": \"CVE ID : CVE-2024-49854 \nPublished : Oct. 21, 2024, 1:15 p.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nblock, bfq: fix uaf for accessing waker_bfqq after splitting  \n  \nAfter commit 42c306ed7233 (\"block, bfq: don't break merge chain in  \nbfq_split_bfqq()\"), if the current procress is the last holder of bfqq,  \nthe bfqq can be freed after bfq_split_bfqq(). Hence recored the bfqq and  \nthen access bfqq->waker_bfqq may trigger UAF. What's more, the waker_bfqq  \nmay in the merge chain of bfqq, hence just recored waker_bfqq is still  \nnot safe.  \n  \nFix the problem by adding a helper bfq_waker_bfqq() to check if  \nbfqq->waker_bfqq is in the merge chain, and current procress is the only  \nholder. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T16:00:54.000000Z"}]}