https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 04 Jun 2026 03:30:24 +0000 https://vulnerability.circl.lu/sighting/5c700985-a440-4223-a557-424fe3bf5521/export {"uuid": "5c700985-a440-4223-a557-424fe3bf5521", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52903", "type": "seen", "source": "https://t.me/cvedetector/3751", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-52903 - In the Linux kernel, the following vulnerability h\", \n \"Content\": \"CVE ID : CVE-2023-52903 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nio_uring: lock overflowing for IOPOLL \n \nsyzbot reports an issue with overflow filling for IOPOLL: \n \nWARNING: CPU: 0 PID: 28 at io_uring/io_uring.c:734 io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 \nCPU: 0 PID: 28 Comm: kworker/u4:1 Not tainted 6.2.0-rc3-syzkaller-16369-g358a161a6a9e #0 \nWorkqueue: events_unbound io_ring_exit_work \nCall trace: \n\u00a0io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 \n\u00a0io_req_cqe_overflow+0x5c/0x70 io_uring/io_uring.c:773 \n\u00a0io_fill_cqe_req io_uring/io_uring.h:168 [inline] \n\u00a0io_do_iopoll+0x474/0x62c io_uring/rw.c:1065 \n\u00a0io_iopoll_try_reap_events+0x6c/0x108 io_uring/io_uring.c:1513 \n\u00a0io_uring_try_cancel_requests+0x13c/0x258 io_uring/io_uring.c:3056 \n\u00a0io_ring_exit_work+0xec/0x390 io_uring/io_uring.c:2869 \n\u00a0process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 \n\u00a0worker_thread+0x340/0x610 kernel/workqueue.c:2436 \n\u00a0kthread+0x12c/0x158 kernel/kthread.c:376 \n\u00a0ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863 \n \nThere is no real problem for normal IOPOLL as flush is also called with \nuring_lock taken, but it's getting more complicated for IOPOLL|SQPOLL, \nfor which __io_cqring_overflow_flush() happens from the CQ waiting path. \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:15.000000Z"} {"uuid": "5c700985-a440-4223-a557-424fe3bf5521", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52903", "type": "seen", "source": "https://t.me/cvedetector/3751", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-52903 - In the Linux kernel, the following vulnerability h\", \n \"Content\": \"CVE ID : CVE-2023-52903 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nio_uring: lock overflowing for IOPOLL \n \nsyzbot reports an issue with overflow filling for IOPOLL: \n \nWARNING: CPU: 0 PID: 28 at io_uring/io_uring.c:734 io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 \nCPU: 0 PID: 28 Comm: kworker/u4:1 Not tainted 6.2.0-rc3-syzkaller-16369-g358a161a6a9e #0 \nWorkqueue: events_unbound io_ring_exit_work \nCall trace: \n\u00a0io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 \n\u00a0io_req_cqe_overflow+0x5c/0x70 io_uring/io_uring.c:773 \n\u00a0io_fill_cqe_req io_uring/io_uring.h:168 [inline] \n\u00a0io_do_iopoll+0x474/0x62c io_uring/rw.c:1065 \n\u00a0io_iopoll_try_reap_events+0x6c/0x108 io_uring/io_uring.c:1513 \n\u00a0io_uring_try_cancel_requests+0x13c/0x258 io_uring/io_uring.c:3056 \n\u00a0io_ring_exit_work+0xec/0x390 io_uring/io_uring.c:2869 \n\u00a0process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 \n\u00a0worker_thread+0x340/0x610 kernel/workqueue.c:2436 \n\u00a0kthread+0x12c/0x158 kernel/kthread.c:376 \n\u00a0ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863 \n \nThere is no real problem for normal IOPOLL as flush is also called with \nuring_lock taken, but it's getting more complicated for IOPOLL|SQPOLL, \nfor which __io_cqring_overflow_flush() happens from the CQ waiting path. \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:15.000000Z"} https://vulnerability.circl.lu/sighting/5c700985-a440-4223-a557-424fe3bf5521/export Wed, 21 Aug 2024 09:52:15 +0000 https://vulnerability.circl.lu/sighting/613fb23e-bd87-47db-9611-ff6dcfc44209/export {"uuid": "613fb23e-bd87-47db-9611-ff6dcfc44209", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2023-52903", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "613fb23e-bd87-47db-9611-ff6dcfc44209", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2023-52903", "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/613fb23e-bd87-47db-9611-ff6dcfc44209/export Wed, 03 Dec 2025 14:14:49 +0000