https://vulnerability.circl.lu/sightings/feed 2026-05-05T23:23:31.364937+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/6277a492-c630-40ea-9ed6-781bc2fe3c3e/export 2026-05-05T23:23:31.726334+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "6277a492-c630-40ea-9ed6-781bc2fe3c3e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52983", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/9152", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-52983\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nblock, bfq: fix uaf for bfqq in bic_set_bfqq()\n\nAfter commit 64dc8c732f5c (\"block, bfq: fix possible uaf for 'bfqq->bic'\"),\nbic->bfqq will be accessed in bic_set_bfqq(), however, in some context\nbic->bfqq will be freed, and bic_set_bfqq() is called with the freed\nbic->bfqq.\n\nFix the problem by always freeing bfqq after bic_set_bfqq().\n\ud83d\udccf Published: 2025-03-27T16:43:21.372Z\n\ud83d\udccf Modified: 2025-03-27T17:08:22.246Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7f77f3dab5066a7c9da73d72d1eee895ff84a8d5\n2. https://git.kernel.org/stable/c/511c922c5bf6c8a166bea826e702336bc2424140\n3. https://git.kernel.org/stable/c/cb1876fc33af26d00efdd473311f1b664c77c44e\n4. https://git.kernel.org/stable/c/b600de2d7d3a16f9007fad1bdae82a3951a26af2", "creation_timestamp": "2025-03-27T17:26:43.000000Z"} 2025-03-27T17:26:43+00:00