{"vulnerability": "cve-2024-5674", "sightings": [{"uuid": "57476f06-aa87-4512-8016-b9f1aec0e2d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56740", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyo5dooa22", "content": "", "creation_timestamp": "2024-12-29T12:15:52.945276Z"}, {"uuid": "68870dfc-ee64-40ad-8bee-20ae7bb5490e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56741", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyo7xxzg25", "content": "", "creation_timestamp": "2024-12-29T12:15:55.756082Z"}, {"uuid": "61af7171-59be-4588-8674-40f7b2875f24", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56742", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoccydf22", "content": "", "creation_timestamp": "2024-12-29T12:15:58.297372Z"}, {"uuid": "e506c9ef-77a4-4dae-ac07-ccb2fd7b5104", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56743", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoej4hv22", "content": "", "creation_timestamp": "2024-12-29T12:16:00.562982Z"}, {"uuid": "c185e942-115c-4a99-ba36-cc4c8bbbb74d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56744", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyogm3zn22", "content": "", "creation_timestamp": "2024-12-29T12:16:02.877196Z"}, {"uuid": "018a99f7-4a1d-4298-b613-b968df96ad1a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56745", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoiszjl2k", "content": "", "creation_timestamp": "2024-12-29T12:16:05.160160Z"}, {"uuid": "14be0626-ca1d-4efe-9fe7-813495b5d187", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56746", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyom3lps2f", "content": "", "creation_timestamp": "2024-12-29T12:16:08.432615Z"}, {"uuid": "3289d242-85f6-47d5-bbbb-dd98de7899c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56747", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoofhlw25", "content": "", "creation_timestamp": "2024-12-29T12:16:11.239335Z"}, {"uuid": "e2349daa-3047-43f6-abaa-33d1fa909a58", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56748", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoqmbm22f", "content": "", "creation_timestamp": "2024-12-29T12:16:13.363013Z"}, {"uuid": "cc7f2807-efc7-4666-b0a3-0f5da435036f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56749", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyosvoqq22", "content": "", "creation_timestamp": "2024-12-29T12:16:15.689679Z"}, {"uuid": "5b6ab16f-7032-4074-a39c-979833f32239", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56741", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736096669051615", "content": "", "creation_timestamp": "2024-12-29T12:25:08.800066Z"}, {"uuid": "d06667f5-3250-472a-9222-63e46067addd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56740", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736096654380537", "content": "", "creation_timestamp": "2024-12-29T12:25:08.889482Z"}, {"uuid": "dbd561aa-7e6c-4c9d-b822-6fb30e054d34", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56742", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736096683183054", "content": "", "creation_timestamp": "2024-12-29T12:25:08.949294Z"}, {"uuid": "361a4d4a-322c-4cee-acb3-d0c7628b8905", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56743", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736096698755835", "content": "", "creation_timestamp": "2024-12-29T12:25:09.123192Z"}, {"uuid": "ed2df072-4e34-40cc-aa7b-97f0e7cd4103", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56740", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113736131935334781", "content": "", "creation_timestamp": "2024-12-29T12:34:06.476339Z"}, {"uuid": "fffd189e-704a-4581-a520-d5ea375a25a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56744", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736155699380786", "content": "", "creation_timestamp": "2024-12-29T12:40:09.467986Z"}, {"uuid": "db755796-198c-4032-a264-af613d7b5598", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56745", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736155714636462", "content": "", "creation_timestamp": "2024-12-29T12:40:09.567420Z"}, {"uuid": "34af70c5-6c77-42dc-a833-654e796d17c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56747", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736155746774270", "content": "", "creation_timestamp": "2024-12-29T12:40:10.034968Z"}, {"uuid": "27529c41-a167-4939-9aea-fc90de464f5b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56746", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736155730987491", "content": "", "creation_timestamp": "2024-12-29T12:40:10.111906Z"}, {"uuid": "4b161b4a-73ef-422d-828b-2112eb67e34c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56748", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736214744018973", "content": "", "creation_timestamp": "2024-12-29T12:55:10.230041Z"}, {"uuid": "cbe5b997-74d4-4a70-8c39-5229b6727406", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56749", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736214758415313", "content": "", "creation_timestamp": "2024-12-29T12:55:10.467653Z"}, {"uuid": "c478a38f-53f0-43e5-ab20-c82aa3d522f1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56748", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "f62bc85d-e26d-46b2-bc55-13d7b4bd83de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56741", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "174faec6-c11f-43b2-a3d7-64acc92c412c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56746", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "2db25279-1127-4fad-aadf-8c76280cdce3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56747", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}, {"uuid": "40a4be63-b473-4904-8d25-60c5b55d8457", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56744", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "491a4eb7-f730-4e30-a1b1-019d71c7b66d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56741", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/6157", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-56741\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: No description available\n\ud83d\udccf Published: 2024-12-29T11:30:09.843Z\n\ud83d\udccf Modified: 2025-03-03T08:12:43.495Z\n\ud83d\udd17 References:\nNo references available.", "creation_timestamp": "2025-03-03T08:29:24.000000Z"}, {"uuid": "7ecac542-e331-4e64-8436-fb97d5ed419e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56748", "type": "seen", "source": "https://t.me/cvedetector/13876", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56748 - Qualcomms QEFDMemoryLeak(Vulnerability)\", \n  \"Content\": \"CVE ID : CVE-2024-56748 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb()  \n  \nHook \"qed_ops->common->sb_init = qed_sb_init\" does not release the DMA  \nmemory sb_virt when it fails. Add dma_free_coherent() to free it. This  \nis the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:03.000000Z"}, {"uuid": "08c56a19-e720-4531-8dc8-f8d8134ae327", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56741", "type": "seen", "source": "https://t.me/cvedetector/13888", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56741 - Linux Kernel AppArmor Memory Leak\", \n  \"Content\": \"CVE ID : CVE-2024-56741 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \napparmor: test: Fix memory leak for aa_unpack_strdup()  \n  \nThe string allocated by kmemdup() in aa_unpack_strdup() is not  \nfreed and cause following memory leaks, free them to fix it.  \n  \n unreferenced object 0xffffff80c6af8a50 (size 8):  \n   comm \"kunit_try_catch\", pid 225, jiffies 4294894407  \n   hex dump (first 8 bytes):  \n     74 65 73 74 69 6e 67 00                          testing.  \n   backtrace (crc 5eab668b):  \n     [<0000000001e3714d] kmemleak_alloc+0x34/0x40  \n     [<000000006e6c7776] __kmalloc_node_track_caller_noprof+0x300/0x3e0  \n     [<000000006870467c] kmemdup_noprof+0x34/0x60  \n     [<000000001176bb03] aa_unpack_strdup+0xd0/0x18c  \n     [<000000008ecde918] policy_unpack_test_unpack_strdup_with_null_name+0xf8/0x3ec  \n     [<0000000032ef8f77] kunit_try_run_case+0x13c/0x3ac  \n     [<00000000f3edea23] kunit_generic_run_threadfn_adapter+0x80/0xec  \n     [<00000000adf936cf] kthread+0x2e8/0x374  \n     [<0000000041bb1628] ret_from_fork+0x10/0x20  \n unreferenced object 0xffffff80c2a29090 (size 8):  \n   comm \"kunit_try_catch\", pid 227, jiffies 4294894409  \n   hex dump (first 8 bytes):  \n     74 65 73 74 69 6e 67 00                          testing.  \n   backtrace (crc 5eab668b):  \n     [<0000000001e3714d] kmemleak_alloc+0x34/0x40  \n     [<000000006e6c7776] __kmalloc_node_track_caller_noprof+0x300/0x3e0  \n     [<000000006870467c] kmemdup_noprof+0x34/0x60  \n     [<000000001176bb03] aa_unpack_strdup+0xd0/0x18c  \n     [<0000000046a45c1a] policy_unpack_test_unpack_strdup_with_name+0xd0/0x3c4  \n     [<0000000032ef8f77] kunit_try_run_case+0x13c/0x3ac  \n     [<00000000f3edea23] kunit_generic_run_threadfn_adapter+0x80/0xec  \n     [<00000000adf936cf] kthread+0x2e8/0x374  \n     [<0000000041bb1628] ret_from_fork+0x10/0x20 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:19.000000Z"}, {"uuid": "1bbada05-4eef-412e-919b-ba9d9804e64b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56740", "type": "seen", "source": "https://t.me/cvedetector/13886", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56740 - Linux Kernel NFS LocalIO Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56740 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfs/localio: must clear res.replen in nfs_local_read_done  \n  \nOtherwise memory corruption can occur due to NFSv3 LOCALIO reads  \nleaving garbage in res.replen:  \n- nfs3_read_done() copies that into server->read_hdrsize; from there  \n  nfs3_proc_read_setup() copies it to args.replen in new requests.  \n- nfs3_xdr_enc_read3args() passes that to rpc_prepare_reply_pages()  \n  which includes it in hdrsize for xdr_init_pages, so that rq_rcv_buf  \n  contains a ridiculous len.  \n- This is copied to rq_private_buf and xs_read_stream_request()  \n  eventually passes the kvec to sock_recvmsg() which receives incoming  \n  data into entirely the wrong place.  \n  \nThis is easily reproduced with NFSv3 LOCALIO that is servicing reads  \nwhen it is made to pivot back to using normal RPC.  This switch back  \nto using normal NFSv3 with RPC can occur for a few reasons but this  \nissue was exposed with a test that stops and then restarts the NFSv3  \nserver while LOCALIO is performing heavy read IO. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:18.000000Z"}, {"uuid": "6f3c9514-f5cc-4546-b09e-ac924b38ef4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56747", "type": "seen", "source": "https://t.me/cvedetector/13884", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56747 - CiscoNetworkDevices DMA Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56747 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nscsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()  \n  \nHook \"qedi_ops->common->sb_init = qed_sb_init\" does not release the DMA  \nmemory sb_virt when it fails. Add dma_free_coherent() to free it. This  \nis the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:16.000000Z"}, {"uuid": "0a3430a2-d7fa-420d-b4d4-8cfe141bc615", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56746", "type": "seen", "source": "https://t.me/cvedetector/13883", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56746 - System-on-Chip (SoC) Linux Driver Memory Leak\", \n  \"Content\": \"CVE ID : CVE-2024-56746 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()  \n  \nWhen information such as info->screen_base is not ready, calling  \nsh7760fb_free_mem() does not release memory correctly. Call  \ndma_free_coherent() instead. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:12.000000Z"}, {"uuid": "4db1a3ec-0478-407f-8036-94c7cacece71", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56744", "type": "seen", "source": "https://t.me/cvedetector/13893", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56744 - \"F2FS Linux Kernel Deadlock Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56744 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to avoid potential deadlock in f2fs_record_stop_reason()  \n  \nsyzbot reports deadlock issue of f2fs as below:  \n  \n======================================================  \nWARNING: possible circular locking dependency detected  \n6.12.0-rc3-syzkaller-00087-gc964ced77262 #0 Not tainted  \n------------------------------------------------------  \nkswapd0/79 is trying to acquire lock:  \nffff888011824088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2199 [inline]  \nffff888011824088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_record_stop_reason+0x52/0x1d0 fs/f2fs/super.c:4068  \n  \nbut task is already holding lock:  \nffff88804bd92610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x662/0x15c0 fs/f2fs/inode.c:842  \n  \nwhich lock already depends on the new lock.  \n  \nthe existing dependency chain (in reverse order) is:  \n  \n-> #2 (sb_internal#2){.+.+}-{0:0}:  \n       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825  \n       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]  \n       __sb_start_write include/linux/fs.h:1716 [inline]  \n       sb_start_intwrite+0x4d/0x1c0 include/linux/fs.h:1899  \n       f2fs_evict_inode+0x662/0x15c0 fs/f2fs/inode.c:842  \n       evict+0x4e8/0x9b0 fs/inode.c:725  \n       f2fs_evict_inode+0x1a4/0x15c0 fs/f2fs/inode.c:807  \n       evict+0x4e8/0x9b0 fs/inode.c:725  \n       dispose_list fs/inode.c:774 [inline]  \n       prune_icache_sb+0x239/0x2f0 fs/inode.c:963  \n       super_cache_scan+0x38c/0x4b0 fs/super.c:223  \n       do_shrink_slab+0x701/0x1160 mm/shrinker.c:435  \n       shrink_slab+0x1093/0x14d0 mm/shrinker.c:662  \n       shrink_one+0x43b/0x850 mm/vmscan.c:4818  \n       shrink_many mm/vmscan.c:4879 [inline]  \n       lru_gen_shrink_node mm/vmscan.c:4957 [inline]  \n       shrink_node+0x3799/0x3de0 mm/vmscan.c:5937  \n       kswapd_shrink_node mm/vmscan.c:6765 [inline]  \n       balance_pgdat mm/vmscan.c:6957 [inline]  \n       kswapd+0x1ca3/0x3700 mm/vmscan.c:7226  \n       kthread+0x2f0/0x390 kernel/kthread.c:389  \n       ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147  \n       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  \n  \n-> #1 (fs_reclaim){+.+.}-{0:0}:  \n       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825  \n       __fs_reclaim_acquire mm/page_alloc.c:3834 [inline]  \n       fs_reclaim_acquire+0x88/0x130 mm/page_alloc.c:3848  \n       might_alloc include/linux/sched/mm.h:318 [inline]  \n       prepare_alloc_pages+0x147/0x5b0 mm/page_alloc.c:4493  \n       __alloc_pages_noprof+0x16f/0x710 mm/page_alloc.c:4722  \n       alloc_pages_mpol_noprof+0x3e8/0x680 mm/mempolicy.c:2265  \n       alloc_pages_noprof mm/mempolicy.c:2345 [inline]  \n       folio_alloc_noprof+0x128/0x180 mm/mempolicy.c:2352  \n       filemap_alloc_folio_noprof+0xdf/0x500 mm/filemap.c:1010  \n       do_read_cache_folio+0x2eb/0x850 mm/filemap.c:3787  \n       read_mapping_folio include/linux/pagemap.h:1011 [inline]  \n       f2fs_commit_super+0x3c0/0x7d0 fs/f2fs/super.c:4032  \n       f2fs_record_stop_reason+0x13b/0x1d0 fs/f2fs/super.c:4079  \n       f2fs_handle_critical_error+0x2ac/0x5c0 fs/f2fs/super.c:4174  \n       f2fs_write_inode+0x35f/0x4d0 fs/f2fs/inode.c:785  \n       write_inode fs/fs-writeback.c:1503 [inline]  \n       __writeback_single_inode+0x711/0x10d0 fs/fs-writeback.c:1723  \n       writeback_single_inode+0x1f3/0x660 fs/fs-writeback.c:1779  \n       sync_inode_metadata+0xc4/0x120 fs/fs-writeback.c:2849  \n       f2fs_release_file+0xa8/0x100 fs/f2fs/file.c:1941  \n       __fput+0x23f/0x880 fs/file_table.c:431  \n       task_work_run+0x24f/0x310 kernel/task_work.c:228  \n       resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]  \n       exit_to_user_mode_loop kernel/entry/common.c:114 [inline]  \n       exit_to_user_mode_prepare include/l[...]", "creation_timestamp": "2024-12-29T14:02:26.000000Z"}, {"uuid": "a07f2022-332e-487e-aa31-c7eabe9c48a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56745", "type": "seen", "source": "https://t.me/cvedetector/13892", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56745 - Linux PCI Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56745 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nPCI: Fix reset_method_store() memory leak  \n  \nIn reset_method_store(), a string is allocated via kstrndup() and assigned  \nto the local \"options\". options is then used in with strsep() to find  \nspaces:  \n  \n  while ((name = strsep(&options, \" \")) != NULL) {  \n  \nIf there are no remaining spaces, then options is set to NULL by strsep(),  \nso the subsequent kfree(options) doesn't free the memory allocated via  \nkstrndup().  \n  \nFix by using a separate tmp_options to iterate with strsep() so options is  \npreserved. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:25.000000Z"}, {"uuid": "89d78cd0-8f63-4419-86a7-fec90b0c1990", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56743", "type": "seen", "source": "https://t.me/cvedetector/13890", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56743 - Linux Kernel: NFS Common Remote Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56743 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfs_common: must not hold RCU while calling nfsd_file_put_local  \n  \nMove holding the RCU from nfs_to_nfsd_file_put_local to  \nnfs_to_nfsd_net_put.  It is the call to nfs_to->nfsd_serv_put that  \nrequires the RCU anyway (the puts for nfsd_file and netns were  \ncombined to avoid an extra indirect reference but that  \nmicro-optimization isn't possible now).  \n  \nThis fixes xfstests generic/013 and it triggering:  \n  \n\"Voluntary context switch within RCU read-side critical section!\"  \n  \n[  143.545738] Call Trace:  \n[  143.546206]    \n[  143.546625]  ? show_regs+0x6d/0x80  \n[  143.547267]  ? __warn+0x91/0x140  \n[  143.547951]  ? rcu_note_context_switch+0x496/0x5d0  \n[  143.548856]  ? report_bug+0x193/0x1a0  \n[  143.549557]  ? handle_bug+0x63/0xa0  \n[  143.550214]  ? exc_invalid_op+0x1d/0x80  \n[  143.550938]  ? asm_exc_invalid_op+0x1f/0x30  \n[  143.551736]  ? rcu_note_context_switch+0x496/0x5d0  \n[  143.552634]  ? wakeup_preempt+0x62/0x70  \n[  143.553358]  __schedule+0xaa/0x1380  \n[  143.554025]  ? _raw_spin_unlock_irqrestore+0x12/0x40  \n[  143.554958]  ? try_to_wake_up+0x1fe/0x6b0  \n[  143.555715]  ? wake_up_process+0x19/0x20  \n[  143.556452]  schedule+0x2e/0x120  \n[  143.557066]  schedule_preempt_disabled+0x19/0x30  \n[  143.557933]  rwsem_down_read_slowpath+0x24d/0x4a0  \n[  143.558818]  ? xfs_efi_item_format+0x50/0xc0 [xfs]  \n[  143.559894]  down_read+0x4e/0xb0  \n[  143.560519]  xlog_cil_commit+0x1b2/0xbc0 [xfs]  \n[  143.561460]  ? _raw_spin_unlock+0x12/0x30  \n[  143.562212]  ? xfs_inode_item_precommit+0xc7/0x220 [xfs]  \n[  143.563309]  ? xfs_trans_run_precommits+0x69/0xd0 [xfs]  \n[  143.564394]  __xfs_trans_commit+0xb5/0x330 [xfs]  \n[  143.565367]  xfs_trans_roll+0x48/0xc0 [xfs]  \n[  143.566262]  xfs_defer_trans_roll+0x57/0x100 [xfs]  \n[  143.567278]  xfs_defer_finish_noroll+0x27a/0x490 [xfs]  \n[  143.568342]  xfs_defer_finish+0x1a/0x80 [xfs]  \n[  143.569267]  xfs_bunmapi_range+0x4d/0xb0 [xfs]  \n[  143.570208]  xfs_itruncate_extents_flags+0x13d/0x230 [xfs]  \n[  143.571353]  xfs_free_eofblocks+0x12e/0x190 [xfs]  \n[  143.572359]  xfs_file_release+0x12d/0x140 [xfs]  \n[  143.573324]  __fput+0xe8/0x2d0  \n[  143.573922]  __fput_sync+0x1d/0x30  \n[  143.574574]  nfsd_filp_close+0x33/0x60 [nfsd]  \n[  143.575430]  nfsd_file_free+0x96/0x150 [nfsd]  \n[  143.576274]  nfsd_file_put+0xf7/0x1a0 [nfsd]  \n[  143.577104]  nfsd_file_put_local+0x18/0x30 [nfsd]  \n[  143.578070]  nfs_close_local_fh+0x101/0x110 [nfs_localio]  \n[  143.579079]  __put_nfs_open_context+0xc9/0x180 [nfs]  \n[  143.580031]  nfs_file_clear_open_context+0x4a/0x60 [nfs]  \n[  143.581038]  nfs_file_release+0x3e/0x60 [nfs]  \n[  143.581879]  __fput+0xe8/0x2d0  \n[  143.582464]  __fput_sync+0x1d/0x30  \n[  143.583108]  __x64_sys_close+0x41/0x80  \n[  143.583823]  x64_sys_call+0x189a/0x20d0  \n[  143.584552]  do_syscall_64+0x64/0x170  \n[  143.585240]  entry_SYSCALL_64_after_hwframe+0x76/0x7e  \n[  143.586185] RIP: 0033:0x7f3c5153efd7 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:23.000000Z"}, {"uuid": "6dbd53ca-f2db-4487-b5f0-d26e04a97b23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56742", "type": "seen", "source": "https://t.me/cvedetector/13889", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56742 - VMware ESXi Linux Kernel Out-of-Bounds Unwind\", \n  \"Content\": \"CVE ID : CVE-2024-56742 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages()  \n  \nFix an unwind issue in mlx5vf_add_migration_pages().  \n  \nIf a set of pages is allocated but fails to be added to the SG table,  \nthey need to be freed to prevent a memory leak.  \n  \nAny pages successfully added to the SG table will be freed as part of  \nmlx5vf_free_data_buffer(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:23.000000Z"}, {"uuid": "0c6f0443-e552-4b28-bba8-21da274471a4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56749", "type": "seen", "source": "https://t.me/cvedetector/13877", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56749 - \"Linux DLM Remote Crash Impact Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56749 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndlm: fix dlm_recover_members refcount on error  \n  \nIf dlm_recover_members() fails we don't drop the references of the  \nprevious created root_list that holds and keep all rsbs alive during the  \nrecovery. It might be not an unlikely event because ping_members() could  \nrun into an -EINTR if another recovery progress was triggered again. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T14:02:04.000000Z"}]}