{"vulnerability": "cve-2024-5675", "sightings": [{"uuid": "295b363b-6437-45bd-82ac-308597695100", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opb7fac2b", "content": "", "creation_timestamp": "2025-01-06T17:43:28.159089Z"}, {"uuid": "1d5693df-6a41-4e38-ba29-b4a3d2e8dfa9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbxzd22b", "content": "", "creation_timestamp": "2025-01-06T17:43:31.705011Z"}, {"uuid": "b2ffb083-04a0-4a4f-8151-f2621caa5326", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lf3opbrky525", "content": "", "creation_timestamp": "2025-01-06T17:43:30.584281Z"}, {"uuid": "5ebaaa49-2250-433a-b6b5-64011bc5c073", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56752", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyozrunn22", "content": "", "creation_timestamp": "2024-12-29T12:16:23.224689Z"}, {"uuid": "6e3b6003-34fe-41b7-8ca1-e6cbc4edb752", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56750", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyovhk5l2c", "content": "", "creation_timestamp": "2024-12-29T12:16:18.278968Z"}, {"uuid": "91a38f94-81b7-4f91-a8bf-7a57b3fb10ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyoxmqyw2e", "content": "", "creation_timestamp": "2024-12-29T12:16:20.457543Z"}, {"uuid": "02553f15-f87b-4442-b2e3-d40bd8a03c85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56753", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyp3xuix2a", "content": "", "creation_timestamp": "2024-12-29T12:16:25.089154Z"}, {"uuid": "8f790120-a6e9-4377-a32e-23fe81ed5945", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56754", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legyp6kx7b25", "content": "", "creation_timestamp": "2024-12-29T12:16:27.841657Z"}, {"uuid": "b5f0d6ba-5c1d-47fd-87c7-98cc4520de23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56755", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legypbbgo522", "content": "", "creation_timestamp": "2024-12-29T12:16:30.740645Z"}, {"uuid": "d77ae797-4ccf-41ac-a355-743a1df2ee2c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3legypdnqjs2f", "content": "", "creation_timestamp": "2024-12-29T12:16:33.136197Z"}, {"uuid": "4a491fe3-05af-43d1-8278-7d0fbddd33af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56750", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736214773327301", "content": "", "creation_timestamp": "2024-12-29T12:55:10.651410Z"}, {"uuid": "1dcafab9-38e6-498e-b884-b47b2d0086a7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736214787522231", "content": "", "creation_timestamp": "2024-12-29T12:55:10.872511Z"}, {"uuid": "ae67ac45-ff7a-4a6e-9fb9-f1b0a319892a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56752", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736273789466023", "content": "", "creation_timestamp": "2024-12-29T13:10:11.151737Z"}, {"uuid": "61f16d8d-dad7-4df1-bab9-c0a5d0cf25f9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56753", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736273804157756", "content": "", "creation_timestamp": "2024-12-29T13:10:11.299335Z"}, {"uuid": "6ff84661-65c0-4f2d-be49-0bd401c87410", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56754", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736273819216876", "content": "", "creation_timestamp": "2024-12-29T13:10:11.489198Z"}, {"uuid": "aa1ce480-d0c3-47c3-988f-92780fe40ee1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56755", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736273833535812", "content": "", "creation_timestamp": "2024-12-29T13:10:11.847777Z"}, {"uuid": "86b3af8a-c788-4c71-b9b0-4749f8081404", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113736332831048028", "content": "", "creation_timestamp": "2024-12-29T13:25:12.054591Z"}, {"uuid": "71fa1fc2-ea2f-41f5-acbc-755a75a51c4d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56755", "type": "seen", "source": "https://bsky.app/profile/omo.bsky.social/post/3letf26u7tk2j", "content": "", "creation_timestamp": "2025-01-03T10:29:21.786101Z"}, {"uuid": "800d9c99-44d7-4f44-9c8e-81bd17dad549", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6dsmrp2a", "content": "", "creation_timestamp": "2025-01-06T17:16:06.762502Z"}, {"uuid": "17ff88db-75da-450d-b161-d0275d4f8ff9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6gj5oh2c", "content": "", "creation_timestamp": "2025-01-06T17:16:09.446727Z"}, {"uuid": "f2c345da-60df-421f-a5fa-aa237bbf7c80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lf3n6jb5j622", "content": "", "creation_timestamp": "2025-01-06T17:16:12.370179Z"}, {"uuid": "7cca49b1-7451-4e52-b8ff-cfbeaecc9c1d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56756", "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": "c41e8e67-52ca-4f47-add7-7eae99e0942d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://bsky.app/profile/o2cloud.bsky.social/post/3me6zzvrufd2z", "content": "", "creation_timestamp": "2026-02-06T13:45:16.445791Z"}, {"uuid": "003b9ed8-f581-42ac-bb18-cf0b0feef654", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56754", "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": "6c15e5ed-6be7-4cef-9203-af64d8aae803", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://t.me/cvedetector/14387", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56759 - Linux Btrfs Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56759 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: fix use-after-free when COWing tree bock and tracing is enabled  \n  \nWhen a COWing a tree block, at btrfs_cow_block(), and we have the  \ntracepoint trace_btrfs_cow_block() enabled and preemption is also enabled  \n(CONFIG_PREEMPT=y), we can trigger a use-after-free in the COWed extent  \nbuffer while inside the tracepoint code. This is because in some paths  \nthat call btrfs_cow_block(), such as btrfs_search_slot(), we are holding  \nthe last reference on the extent buffer @buf so btrfs_force_cow_block()  \ndrops the last reference on the @buf extent buffer when it calls  \nfree_extent_buffer_stale(buf), which schedules the release of the extent  \nbuffer with RCU. This means that if we are on a kernel with preemption,  \nthe current task may be preempted before calling trace_btrfs_cow_block()  \nand the extent buffer already released by the time trace_btrfs_cow_block()  \nis called, resulting in a use-after-free.  \n  \nFix this by moving the trace_btrfs_cow_block() from btrfs_cow_block() to  \nbtrfs_force_cow_block() before the COWed extent buffer is freed.  \nThis also has a side effect of invoking the tracepoint in the tree defrag  \ncode, at defrag.c:btrfs_realloc_node(), since btrfs_force_cow_block() is  \ncalled there, but this is fine and it was actually missing there. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:46.000000Z"}, {"uuid": "1aa34a9f-91d5-478d-b978-dfb5f75af6d0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "396d93dd-edbb-41f3-a2be-2e3e914df8ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://t.me/cvedetector/14385", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56757 - \"Mediatek Bluetooth btusb Kernel Panic Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56757 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: btusb: mediatek: add intf release flow when usb disconnect  \n  \nMediaTek claim an special usb intr interface for ISO data transmission.  \nThe interface need to be released before unregistering hci device when  \nusb disconnect. Removing BT usb dongle without properly releasing the  \ninterface may cause Kernel panic while unregister hci device. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:44.000000Z"}, {"uuid": "7e864b35-2435-4c49-bc12-1b5a970ae256", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-56757", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "a089100a-2da2-458a-a789-9456729fd989", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-56759", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1e72e3c3-1ca0-4d21-b491-0ee509125220", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56758", "type": "seen", "source": "https://t.me/cvedetector/14386", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56758 - Linux Btrfs NULL Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56758 \nPublished : Jan. 6, 2025, 5:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: check folio mapping after unlock in relocate_one_folio()  \n  \nWhen we call btrfs_read_folio() to bring a folio uptodate, we unlock the  \nfolio. The result of that is that a different thread can modify the  \nmapping (like remove it with invalidate) before we call folio_lock().  \nThis results in an invalid page and we need to try again.  \n  \nIn particular, if we are relocating concurrently with aborting a  \ntransaction, this can result in a crash like the following:  \n  \n  BUG: kernel NULL pointer dereference, address: 0000000000000000  \n  PGD 0 P4D 0  \n  Oops: 0000 [#1] SMP  \n  CPU: 76 PID: 1411631 Comm: kworker/u322:5  \n  Workqueue: events_unbound btrfs_reclaim_bgs_work  \n  RIP: 0010:set_page_extent_mapped+0x20/0xb0  \n  RSP: 0018:ffffc900516a7be8 EFLAGS: 00010246  \n  RAX: ffffea009e851d08 RBX: ffffea009e0b1880 RCX: 0000000000000000  \n  RDX: 0000000000000000 RSI: ffffc900516a7b90 RDI: ffffea009e0b1880  \n  RBP: 0000000003573000 R08: 0000000000000001 R09: ffff88c07fd2f3f0  \n  R10: 0000000000000000 R11: 0000194754b575be R12: 0000000003572000  \n  R13: 0000000003572fff R14: 0000000000100cca R15: 0000000005582fff  \n  FS:  0000000000000000(0000) GS:ffff88c07fd00000(0000) knlGS:0000000000000000  \n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n  CR2: 0000000000000000 CR3: 000000407d00f002 CR4: 00000000007706f0  \n  DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \n  DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n  PKRU: 55555554  \n  Call Trace:  \n    \n  ? __die+0x78/0xc0  \n  ? page_fault_oops+0x2a8/0x3a0  \n  ? __switch_to+0x133/0x530  \n  ? wq_worker_running+0xa/0x40  \n  ? exc_page_fault+0x63/0x130  \n  ? asm_exc_page_fault+0x22/0x30  \n  ? set_page_extent_mapped+0x20/0xb0  \n  relocate_file_extent_cluster+0x1a7/0x940  \n  relocate_data_extent+0xaf/0x120  \n  relocate_block_group+0x20f/0x480  \n  btrfs_relocate_block_group+0x152/0x320  \n  btrfs_relocate_chunk+0x3d/0x120  \n  btrfs_reclaim_bgs_work+0x2ae/0x4e0  \n  process_scheduled_works+0x184/0x370  \n  worker_thread+0xc6/0x3e0  \n  ? blk_add_timer+0xb0/0xb0  \n  kthread+0xae/0xe0  \n  ? flush_tlb_kernel_range+0x90/0x90  \n  ret_from_fork+0x2f/0x40  \n  ? flush_tlb_kernel_range+0x90/0x90  \n  ret_from_fork_asm+0x11/0x20  \n    \n  \nThis occurs because cleanup_one_transaction() calls  \ndestroy_delalloc_inodes() which calls invalidate_inode_pages2() which  \ntakes the folio_lock before setting mapping to NULL. We fail to check  \nthis, and subsequently call set_extent_mapping(), which assumes that  \nmapping != NULL (in fact it asserts that in debug mode)  \n  \nNote that the \"fixes\" patch here is not the one that introduced the  \nrace (the very first iteration of this code from 2009) but a more recent  \nchange that made this particular crash happen in practice. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"06 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-06T19:26:45.000000Z"}, {"uuid": "59955820-5b4f-43f9-a870-23e46cfb2506", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56754", "type": "seen", "source": "https://t.me/cvedetector/13882", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56754 - Apache CAAM Type Confusion\", \n  \"Content\": \"CVE ID : CVE-2024-56754 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncrypto: caam - Fix the pointer passed to caam_qi_shutdown()  \n  \nThe type of the last parameter given to devm_add_action_or_reset() is  \n\"struct caam_drv_private *\", but in caam_qi_shutdown(), it is casted to  \n\"struct device *\".  \n  \nPass the correct parameter to devm_add_action_or_reset() so that the  \nresources are released as expected. \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:11.000000Z"}, {"uuid": "590034c1-5daf-471a-ab56-09594bcab296", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56753", "type": "seen", "source": "https://t.me/cvedetector/13881", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56753 - AMD GPU Cleaning Deinitialization Memory Leak\", \n  \"Content\": \"CVE ID : CVE-2024-56753 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amdgpu/gfx9: Add Cleaner Shader Deinitialization in gfx_v9_0 Module  \n  \nThis commit addresses an omission in the previous patch related to the  \ncleaner shader support for GFX9 hardware. Specifically, it adds the  \nnecessary deinitialization code for the cleaner shader in the  \ngfx_v9_0_sw_fini function.  \n  \nThe added line amdgpu_gfx_cleaner_shader_sw_fini(adev); ensures that any  \nallocated resources for the cleaner shader are freed correctly, avoiding  \npotential memory leaks and ensuring that the GPU state is clean for the  \nnext initialization sequence. \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:10.000000Z"}, {"uuid": "b8010335-7cea-48ab-8db1-3157e022bf75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56752", "type": "seen", "source": "https://t.me/cvedetector/13880", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56752 - NVIDIA GPU Missing Unlock State Change\", \n  \"Content\": \"CVE ID : CVE-2024-56752 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/nouveau/gr/gf100: Fix missing unlock in gf100_gr_chan_new()  \n  \nWhen the call to gf100_grctx_generate() fails, unlock gr->fecs.mutex  \nbefore returning the error.  \n  \nFixes smatch warning:  \n  \ndrivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:480 gf100_gr_chan_new() warn: inconsistent returns '&gr->fecs.mutex'. \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:09.000000Z"}, {"uuid": "fc6f0ca6-dba0-4409-b7cb-333ee725ab90", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56751", "type": "seen", "source": "https://t.me/cvedetector/13879", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56751 - \"Linux Kernel IPv6 Nexthop Leaks Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56751 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nipv6: release nexthop on device removal  \n  \nThe CI is hitting some aperiodic hangup at device removal time in the  \npmtu.sh self-test:  \n  \nunregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6  \nref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at  \n dst_init+0x84/0x4a0  \n dst_alloc+0x97/0x150  \n ip6_dst_alloc+0x23/0x90  \n ip6_rt_pcpu_alloc+0x1e6/0x520  \n ip6_pol_route+0x56f/0x840  \n fib6_rule_lookup+0x334/0x630  \n ip6_route_output_flags+0x259/0x480  \n ip6_dst_lookup_tail.constprop.0+0x5c2/0x940  \n ip6_dst_lookup_flow+0x88/0x190  \n udp_tunnel6_dst_lookup+0x2a7/0x4c0  \n vxlan_xmit_one+0xbde/0x4a50 [vxlan]  \n vxlan_xmit+0x9ad/0xf20 [vxlan]  \n dev_hard_start_xmit+0x10e/0x360  \n __dev_queue_xmit+0xf95/0x18c0  \n arp_solicit+0x4a2/0xe00  \n neigh_probe+0xaa/0xf0  \n  \nWhile the first suspect is the dst_cache, explicitly tracking the dst  \nowing the last device reference via probes proved such dst is held by  \nthe nexthop in the originating fib6_info.  \n  \nSimilar to commit f5b51fe804ec (\"ipv6: route: purge exception on  \nremoval\"), we need to explicitly release the originating fib info when  \ndisconnecting a to-be-removed device from a live ipv6 dst: move the  \nfib6_info cleanup into ip6_dst_ifdown().  \n  \nTested running:  \n  \n./pmtu.sh cleanup_ipv6_exception  \n  \nin a tight loop for more than 400 iterations with no spat, running an  \nunpatched kernel  I observed a splat every ~10 iterations. \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:09.000000Z"}, {"uuid": "002323b9-2835-4f9f-85d1-2a0f6a3ed50d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56750", "type": "seen", "source": "https://t.me/cvedetector/13878", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56750 - Android EROFS Block Size Validation Issue\", \n  \"Content\": \"CVE ID : CVE-2024-56750 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nerofs: fix blksize < PAGE_SIZE for file-backed mounts  \n  \nAdjust sb->s_blocksize{,_bits} directly for file-backed  \nmounts when the fs block size is smaller than PAGE_SIZE.  \n  \nPreviously, EROFS used sb_set_blocksize(), which caused  \na panic if bdev-backed mounts is not used. \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:05.000000Z"}, {"uuid": "7aa134e4-eddf-45a9-9a7d-5b1f1baa5f6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56756", "type": "seen", "source": "https://t.me/cvedetector/13875", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56756 - \"Nvidia NVMe Host Memory Buffer Descriptor Table DMA Free Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-56756 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvme-pci: fix freeing of the HMB descriptor table  \n  \nThe HMB descriptor table is sized to the maximum number of descriptors  \nthat could be used for a given device, but __nvme_alloc_host_mem could  \nbreak out of the loop earlier on memory allocation failure and end up  \nusing less descriptors than planned for, which leads to an incorrect  \nsize passed to dma_free_coherent.  \n  \nIn practice this was not showing up because the number of descriptors  \ntends to be low and the dma coherent allocator always allocates and  \nfrees at least a page. \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": "1bdef6b3-652e-46eb-8aa7-8bc0006e073b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56755", "type": "seen", "source": "https://t.me/cvedetector/13874", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56755 - Apache Linux Kernel Double-Submission Race Condition\", \n  \"Content\": \"CVE ID : CVE-2024-56755 \nPublished : Dec. 29, 2024, 12:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING  \n  \nIn fscache_create_volume(), there is a missing memory barrier between the  \nbit-clearing operation and the wake-up operation. This may cause a  \nsituation where, after a wake-up, the bit-clearing operation hasn't been  \ndetected yet, leading to an indefinite wait. The triggering process is as  \nfollows:  \n  \n  [cookie1]                [cookie2]                  [volume_work]  \nfscache_perform_lookup  \n  fscache_create_volume  \n                        fscache_perform_lookup  \n                          fscache_create_volume  \n                           fscache_create_volume_work  \n                                                  cachefiles_acquire_volume  \n                                                  clear_and_wake_up_bit  \n    test_and_set_bit  \n                            test_and_set_bit  \n                              goto maybe_wait  \n      goto no_wait  \n  \nIn the above process, cookie1 and cookie2 has the same volume. When cookie1  \nenters the -no_wait- process, it will clear the bit and wake up the waiting  \nprocess. If a barrier is missing, it may cause cookie2 to remain in the  \n-wait- process indefinitely.  \n  \nIn commit 3288666c7256 (\"fscache: Use clear_and_wake_up_bit() in  \nfscache_create_volume_work()\"), barriers were added to similar operations  \nin fscache_create_volume_work(), but fscache_create_volume() was missed.  \n  \nBy combining the clear and wake operations into clear_and_wake_up_bit() to  \nfix this issue. \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:02.000000Z"}]}