{"vulnerability": "CVE-2024-5789", "sightings": [{"uuid": "57b0b771-3d25-4713-a475-c6d272a7697f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57899", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtzfmzug2e", "content": "", "creation_timestamp": "2025-01-15T13:17:11.023033Z"}, {"uuid": "e73ad30a-1771-468b-8104-b7e18c7d7834", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57890", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtyqeeic2r", "content": "", "creation_timestamp": "2025-01-15T13:16:48.529608Z"}, {"uuid": "3cee6f04-96b6-4bf5-bc2b-9943d83cc7d6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57891", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtytbh4w2e", "content": "", "creation_timestamp": "2025-01-15T13:16:51.683099Z"}, {"uuid": "a0b8dd73-3a65-48d7-bae8-9ac552bb036d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57894", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtz2apwf2t", "content": "", "creation_timestamp": "2025-01-15T13:16:58.961725Z"}, {"uuid": "85cada19-7bf7-4cfb-8107-ee4e9386ecf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtyvorop2n", "content": "", "creation_timestamp": "2025-01-15T13:16:54.064483Z"}, {"uuid": "c733c3a0-4f7b-4f68-ae27-fb353bff8734", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57893", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtyxz2fo2t", "content": "", "creation_timestamp": "2025-01-15T13:16:56.546454Z"}, {"uuid": "10734c51-364e-466a-9cde-38d22b7a7eb5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57895", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtz4fwlw2r", "content": "", "creation_timestamp": "2025-01-15T13:17:01.139551Z"}, {"uuid": "55031141-82e9-467c-838d-e5fce1e1536b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57896", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtz6moib2c", "content": "", "creation_timestamp": "2025-01-15T13:17:03.449451Z"}, {"uuid": "c3be5c85-ad7a-4fa9-87fc-7e87f780c00e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57897", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtzazhmu2p", "content": "", "creation_timestamp": "2025-01-15T13:17:05.977503Z"}, {"uuid": "26d045cc-61f1-4243-83ee-cbc6b8e77154", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtzdgdkr2b", "content": "", "creation_timestamp": "2025-01-15T13:17:08.449826Z"}, {"uuid": "065a2d77-cb1b-4593-9474-a5071fcede84", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfrvq5ymqx2u", "content": "", "creation_timestamp": "2025-01-15T13:47:48.494050Z"}, {"uuid": "d26eb9e4-0425-4f9d-b009-e7a1d74d593c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57899", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfrvq6odww2g", "content": "", "creation_timestamp": "2025-01-15T13:47:49.488340Z"}, {"uuid": "eb2bbcdd-9d8b-48c2-a055-c0d6c47885cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57893", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfrvq7cihw2g", "content": "", "creation_timestamp": "2025-01-15T13:47:51.905418Z"}, {"uuid": "ae64af90-d8f5-410c-85e2-d38fc896dc49", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57895", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0291/", "content": "", "creation_timestamp": "2026-03-13T00:00:00.000000Z"}, {"uuid": "584f017b-70fd-4552-93dd-00e45dd2a0db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57893", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "41365a31-cedf-4d1d-9d20-128827e43997", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57895", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "ff309b4c-aa1e-45d2-80b4-db4c2b60aa26", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "98857dc2-9cbe-4787-b771-f8e16c8f6a48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57899", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "d8cb8c0e-f16d-476d-b8e9-852b4b08561a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57899", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "567f28c7-eb77-420c-8c57-9cea97221323", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57896", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "1248ac2e-30ab-4bc2-a5c3-045bb6e4e642", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57893", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "23ab34a3-4db4-405b-a37e-2714d7fc2101", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "84ae75b9-e780-44c3-9578-be31ebd7b570", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "vulnerability": "CVE-2024-57897", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "d3bc162f-70db-4ae3-b605-c861700e2b8d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2024-57895", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/debian-linux-kernel-multiple-vulnerabilities_20260316", "content": "", "creation_timestamp": "2026-03-16T03:00:00.000000Z"}, {"uuid": "1adbf8a1-789c-4302-b8bf-090090e3380f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57893", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1754", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57893\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: seq: oss: Fix races at processing SysEx messages\n\nOSS sequencer handles the SysEx messages split in 6 bytes packets, and\nALSA sequencer OSS layer tries to combine those.  It stores the data\nin the internal buffer and this access is racy as of now, which may\nlead to the out-of-bounds access.\n\nAs a temporary band-aid fix, introduce a mutex for serializing the\nprocess of the SysEx message packets.\n\ud83d\udccf Published: 2025-01-15T13:05:45.550Z\n\ud83d\udccf Modified: 2025-01-15T13:05:45.550Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cff1de87ed14fc0f2332213d2367100e7ad0753a\n2. https://git.kernel.org/stable/c/d2392b79d8af3714ea8878b71c66dc49d3110f44\n3. https://git.kernel.org/stable/c/9d382112b36382aa65aad765f189ebde9926c101\n4. https://git.kernel.org/stable/c/0179488ca992d79908b8e26b9213f1554fc5bacc", "creation_timestamp": "2025-01-15T14:25:14.000000Z"}, {"uuid": "0ef9b03f-b59a-465c-91cf-38292c42bbbe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57890", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1756", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57890\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/uverbs: Prevent integer overflow issue\n\nIn the expression \"cmd.wqe_size * cmd.wr_count\", both variables are u32\nvalues that come from the user so the multiplication can lead to integer\nwrapping.  Then we pass the result to uverbs_request_next_ptr() which also\ncould potentially wrap.  The \"cmd.sge_count * sizeof(struct ib_uverbs_sge)\"\nmultiplication can also overflow on 32bit systems although it's fine on\n64bit systems.\n\nThis patch does two things.  First, I've re-arranged the condition in\nuverbs_request_next_ptr() so that the use controlled variable \"len\" is on\none side of the comparison by itself without any math.  Then I've modified\nall the callers to use size_mul() for the multiplications.\n\ud83d\udccf Published: 2025-01-15T13:05:42.690Z\n\ud83d\udccf Modified: 2025-01-15T13:05:42.690Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/c57721b24bd897338a81a0ca5fff41600f0f1ad1\n2. https://git.kernel.org/stable/c/42a6eb4ed7a9a41ba0b83eb0c7e0225b5fca5608\n3. https://git.kernel.org/stable/c/c2f961c46ea0e5274c5c320d007c2dd949cf627a\n4. https://git.kernel.org/stable/c/346db03e9926ab7117ed9bf19665699c037c773c\n5. https://git.kernel.org/stable/c/b92667f755749cf10d9ef1088865c555ae83ffb7\n6. https://git.kernel.org/stable/c/b3ef4ae713360501182695dd47d6b4f6e1a43eb8\n7. https://git.kernel.org/stable/c/d0257e089d1bbd35c69b6c97ff73e3690ab149a9", "creation_timestamp": "2025-01-15T14:26:39.000000Z"}, {"uuid": "ac8f5a4b-c5f9-416a-a6b0-bf5e9793fca8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1755", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57892\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv\n\nWhen mounting ocfs2 and then remounting it as read-only, a\nslab-use-after-free occurs after the user uses a syscall to\nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)->dqi_priv is the\ndangling pointer.\n\nDuring the remounting process, the pointer dqi_priv is freed but is never\nset as null leaving it to be accessed.  Additionally, the read-only option\nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the\nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the\nnext quota, the function ocfs2_get_next_id is called and only checks the\nquota usage flags and not the quota suspended flags.\n\nTo fix this, I set dqi_priv to null when it is freed after remounting with\nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.\n\n[akpm@linux-foundation.org: coding-style cleanups]\n\ud83d\udccf Published: 2025-01-15T13:05:44.635Z\n\ud83d\udccf Modified: 2025-01-15T13:05:44.635Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2e3d203b1adede46bbba049e497765d67865be18\n2. https://git.kernel.org/stable/c/ba950a02d8d23811aa1120affd3adedcfac6153d\n3. https://git.kernel.org/stable/c/5f3fd772d152229d94602bca243fbb658068a597", "creation_timestamp": "2025-01-15T14:25:31.000000Z"}, {"uuid": "ab739760-dcb0-435b-afef-81cf719d2318", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1753", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57898\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: clear link ID from bitmap during link delete after clean up\n\nCurrently, during link deletion, the link ID is first removed from the\nvalid_links bitmap before performing any clean-up operations. However, some\nfunctions require the link ID to remain in the valid_links bitmap. One\nsuch example is cfg80211_cac_event(). The flow is -\n\nnl80211_remove_link()\n    cfg80211_remove_link()\n        ieee80211_del_intf_link()\n            ieee80211_vif_set_links()\n                ieee80211_vif_update_links()\n                    ieee80211_link_stop()\n                        cfg80211_cac_event()\n\ncfg80211_cac_event() requires link ID to be present but it is cleared\nalready in cfg80211_remove_link(). Ultimately, WARN_ON() is hit.\n\nTherefore, clear the link ID from the bitmap only after completing the link\nclean-up.\n\ud83d\udccf Published: 2025-01-15T13:05:49.718Z\n\ud83d\udccf Modified: 2025-01-15T13:05:49.718Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ae07daf440d3220d0986e676317a5da66e4f9dfd\n2. https://git.kernel.org/stable/c/b5c32ff6a3a38c74facdd1fe34c0d709a55527fd", "creation_timestamp": "2025-01-15T14:22:18.000000Z"}, {"uuid": "df390441-21d3-430f-a957-55f0670e4443", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57899", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1752", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57899\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: fix mbss changed flags corruption on 32 bit systems\n\nOn 32-bit systems, the size of an unsigned long is 4 bytes,\nwhile a u64 is 8 bytes. Therefore, when using\nor_each_set_bit(bit, &bits, sizeof(changed) * BITS_PER_BYTE),\nthe code is incorrectly searching for a bit in a 32-bit\nvariable that is expected to be 64 bits in size,\nleading to incorrect bit finding.\n\nSolution: Ensure that the size of the bits variable is correctly\nadjusted for each architecture.\n\n Call Trace:\n  ? show_regs+0x54/0x58\n  ? __warn+0x6b/0xd4\n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]\n  ? report_bug+0x113/0x150\n  ? exc_overflow+0x30/0x30\n  ? handle_bug+0x27/0x44\n  ? exc_invalid_op+0x18/0x50\n  ? handle_exception+0xf6/0xf6\n  ? exc_overflow+0x30/0x30\n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]\n  ? exc_overflow+0x30/0x30\n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]\n  ? ieee80211_mesh_work+0xff/0x260 [mac80211]\n  ? cfg80211_wiphy_work+0x72/0x98 [cfg80211]\n  ? process_one_work+0xf1/0x1fc\n  ? worker_thread+0x2c0/0x3b4\n  ? kthread+0xc7/0xf0\n  ? mod_delayed_work_on+0x4c/0x4c\n  ? kthread_complete_and_exit+0x14/0x14\n  ? ret_from_fork+0x24/0x38\n  ? kthread_complete_and_exit+0x14/0x14\n  ? ret_from_fork_asm+0xf/0x14\n  ? entry_INT80_32+0xf0/0xf0\n\n[restore no-op path for no changes]\n\ud83d\udccf Published: 2025-01-15T13:05:50.701Z\n\ud83d\udccf Modified: 2025-01-15T13:05:50.701Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/86772872f9f5097cd03d0e1c6813238bd38c250b\n2. https://git.kernel.org/stable/c/36b739637d7042843f9df57212ecee6ed6e0d4b2\n3. https://git.kernel.org/stable/c/49dba1ded8dd5a6a12748631403240b2ab245c34", "creation_timestamp": "2025-01-15T14:21:29.000000Z"}, {"uuid": "e1484c8b-fc85-4f9e-ab27-cf9fbed4cbb8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57894", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/9280", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57894\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: No description available\n\ud83d\udccf Published: 2025-01-15T13:05:46.564Z\n\ud83d\udccf Modified: 2025-03-28T06:51:10.655Z\n\ud83d\udd17 References:\nNo references available.", "creation_timestamp": "2025-03-28T07:27:26.000000Z"}, {"uuid": "da4bde6a-4e29-43ca-bad6-bcd2d528eca9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57896", "type": "seen", "source": "https://t.me/cvedetector/15452", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57896 - Vulnerability: Intel Linux Kernels btrfs Delalloc Workers Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2024-57896 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: flush delalloc workers queue before stopping cleaner kthread during unmount  \n  \nDuring the unmount path, at close_ctree(), we first stop the cleaner  \nkthread, using kthread_stop() which frees the associated task_struct, and  \nthen stop and destroy all the work queues. However after we stopped the  \ncleaner we may still have a worker from the delalloc_workers queue running  \ninode.c:submit_compressed_extents(), which calls btrfs_add_delayed_iput(),  \nwhich in turn tries to wake up the cleaner kthread - which was already  \ndestroyed before, resulting in a use-after-free on the task_struct.  \n  \nSyzbot reported this with the following stack traces:  \n  \n  BUG: KASAN: slab-use-after-free in __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089  \n  Read of size 8 at addr ffff8880259d2818 by task kworker/u8:3/52  \n  \n  CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.13.0-rc1-syzkaller-00002-gcdd30ebb1b9f #0  \n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024  \n  Workqueue: btrfs-delalloc btrfs_work_helper  \n  Call Trace:  \n     \n   __dump_stack lib/dump_stack.c:94 [inline]  \n   dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120  \n   print_address_description mm/kasan/report.c:378 [inline]  \n   print_report+0x169/0x550 mm/kasan/report.c:489  \n   kasan_report+0x143/0x180 mm/kasan/report.c:602  \n   __lock_acquire+0x78/0x2100 kernel/locking/lockdep.c:5089  \n   lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849  \n   __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]  \n   _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162  \n   class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline]  \n   try_to_wake_up+0xc2/0x1470 kernel/sched/core.c:4205  \n   submit_compressed_extents+0xdf/0x16e0 fs/btrfs/inode.c:1615  \n   run_ordered_work fs/btrfs/async-thread.c:288 [inline]  \n   btrfs_work_helper+0x96f/0xc40 fs/btrfs/async-thread.c:324  \n   process_one_work kernel/workqueue.c:3229 [inline]  \n   process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310  \n   worker_thread+0x870/0xd30 kernel/workqueue.c:3391  \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  \n  Allocated by task 2:  \n   kasan_save_stack mm/kasan/common.c:47 [inline]  \n   kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  \n   unpoison_slab_object mm/kasan/common.c:319 [inline]  \n   __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345  \n   kasan_slab_alloc include/linux/kasan.h:250 [inline]  \n   slab_post_alloc_hook mm/slub.c:4104 [inline]  \n   slab_alloc_node mm/slub.c:4153 [inline]  \n   kmem_cache_alloc_node_noprof+0x1d9/0x380 mm/slub.c:4205  \n   alloc_task_struct_node kernel/fork.c:180 [inline]  \n   dup_task_struct+0x57/0x8c0 kernel/fork.c:1113  \n   copy_process+0x5d1/0x3d50 kernel/fork.c:2225  \n   kernel_clone+0x223/0x870 kernel/fork.c:2807  \n   kernel_thread+0x1bc/0x240 kernel/fork.c:2869  \n   create_kthread kernel/kthread.c:412 [inline]  \n   kthreadd+0x60d/0x810 kernel/kthread.c:767  \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  Freed by task 24:  \n   kasan_save_stack mm/kasan/common.c:47 [inline]  \n   kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  \n   kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:582  \n   poison_slab_object mm/kasan/common.c:247 [inline]  \n   __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264  \n   kasan_slab_free include/linux/kasan.h:233 [inline]  \n   slab_free_hook mm/slub.c:2338 [inline]  \n   slab_free mm/slub.c:4598 [inline]  \n   kmem_cache_free+0x195/0x410 mm/slub.c:4700  \n   put_ta[...]", "creation_timestamp": "2025-01-15T15:06:56.000000Z"}, {"uuid": "82e7f7ce-b731-45cd-a6aa-6064310b7b6f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57895", "type": "seen", "source": "https://t.me/cvedetector/15451", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57895 - Linux kernel: Ksmbd Attribute Ctime Flag Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57895 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nksmbd: set ATTR_CTIME flags when setting mtime  \n  \nDavid reported that the new warning from setattr_copy_mgtime is coming  \nlike the following.  \n  \n[  113.215316] ------------[ cut here ]------------  \n[  113.215974] WARNING: CPU: 1 PID: 31 at fs/attr.c:300 setattr_copy+0x1ee/0x200  \n[  113.219192] CPU: 1 UID: 0 PID: 31 Comm: kworker/1:1 Not tainted 6.13.0-rc1+ #234  \n[  113.220127] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014  \n[  113.221530] Workqueue: ksmbd-io handle_ksmbd_work [ksmbd]  \n[  113.222220] RIP: 0010:setattr_copy+0x1ee/0x200  \n[  113.222833] Code: 24 28 49 8b 44 24 30 48 89 53 58 89 43 6c 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 48 89 df e8 77 d6 ff ff e9 cd fe ff ff <0f0b e9 be fe ff ff 66 0  \n[  113.225110] RSP: 0018:ffffaf218010fb68 EFLAGS: 00010202  \n[  113.225765] RAX: 0000000000000120 RBX: ffffa446815f8568 RCX: 0000000000000003  \n[  113.226667] RDX: ffffaf218010fd38 RSI: ffffa446815f8568 RDI: ffffffff94eb03a0  \n[  113.227531] RBP: ffffaf218010fb90 R08: 0000001a251e217d R09: 00000000675259fa  \n[  113.228426] R10: 0000000002ba8a6d R11: ffffa4468196c7a8 R12: ffffaf218010fd38  \n[  113.229304] R13: 0000000000000120 R14: ffffffff94eb03a0 R15: 0000000000000000  \n[  113.230210] FS:  0000000000000000(0000) GS:ffffa44739d00000(0000) knlGS:0000000000000000  \n[  113.231215] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n[  113.232055] CR2: 00007efe0053d27e CR3: 000000000331a000 CR4: 00000000000006b0  \n[  113.232926] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \n[  113.233812] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400  \n[  113.234797] Call Trace:  \n[  113.235116]    \n[  113.235393]  ? __warn+0x73/0xd0  \n[  113.235802]  ? setattr_copy+0x1ee/0x200  \n[  113.236299]  ? report_bug+0xf3/0x1e0  \n[  113.236757]  ? handle_bug+0x4d/0x90  \n[  113.237202]  ? exc_invalid_op+0x13/0x60  \n[  113.237689]  ? asm_exc_invalid_op+0x16/0x20  \n[  113.238185]  ? setattr_copy+0x1ee/0x200  \n[  113.238692]  btrfs_setattr+0x80/0x820 [btrfs]  \n[  113.239285]  ? get_stack_info_noinstr+0x12/0xf0  \n[  113.239857]  ? __module_address+0x22/0xa0  \n[  113.240368]  ? handle_ksmbd_work+0x6e/0x460 [ksmbd]  \n[  113.240993]  ? __module_text_address+0x9/0x50  \n[  113.241545]  ? __module_address+0x22/0xa0  \n[  113.242033]  ? unwind_next_frame+0x10e/0x920  \n[  113.242600]  ? __pfx_stack_trace_consume_entry+0x10/0x10  \n[  113.243268]  notify_change+0x2c2/0x4e0  \n[  113.243746]  ? stack_depot_save_flags+0x27/0x730  \n[  113.244339]  ? set_file_basic_info+0x130/0x2b0 [ksmbd]  \n[  113.244993]  set_file_basic_info+0x130/0x2b0 [ksmbd]  \n[  113.245613]  ? process_scheduled_works+0xbe/0x310  \n[  113.246181]  ? worker_thread+0x100/0x240  \n[  113.246696]  ? kthread+0xc8/0x100  \n[  113.247126]  ? ret_from_fork+0x2b/0x40  \n[  113.247606]  ? ret_from_fork_asm+0x1a/0x30  \n[  113.248132]  smb2_set_info+0x63f/0xa70 [ksmbd]  \n  \nksmbd is trying to set the atime and mtime via notify_change without also  \nsetting the ctime. so This patch add ATTR_CTIME flags when setting mtime  \nto avoid a warning. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:06:55.000000Z"}, {"uuid": "d474b5d8-bed3-4721-9ca9-ee3d2581979c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57899", "type": "seen", "source": "https://t.me/cvedetector/15446", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57899 - IBM WiFi 802.11 Bitwise Operation Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57899 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: mac80211: fix mbss changed flags corruption on 32 bit systems  \n  \nOn 32-bit systems, the size of an unsigned long is 4 bytes,  \nwhile a u64 is 8 bytes. Therefore, when using  \nor_each_set_bit(bit, &bits, sizeof(changed) * BITS_PER_BYTE),  \nthe code is incorrectly searching for a bit in a 32-bit  \nvariable that is expected to be 64 bits in size,  \nleading to incorrect bit finding.  \n  \nSolution: Ensure that the size of the bits variable is correctly  \nadjusted for each architecture.  \n  \n Call Trace:  \n  ? show_regs+0x54/0x58  \n  ? __warn+0x6b/0xd4  \n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]  \n  ? report_bug+0x113/0x150  \n  ? exc_overflow+0x30/0x30  \n  ? handle_bug+0x27/0x44  \n  ? exc_invalid_op+0x18/0x50  \n  ? handle_exception+0xf6/0xf6  \n  ? exc_overflow+0x30/0x30  \n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]  \n  ? exc_overflow+0x30/0x30  \n  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]  \n  ? ieee80211_mesh_work+0xff/0x260 [mac80211]  \n  ? cfg80211_wiphy_work+0x72/0x98 [cfg80211]  \n  ? process_one_work+0xf1/0x1fc  \n  ? worker_thread+0x2c0/0x3b4  \n  ? kthread+0xc7/0xf0  \n  ? mod_delayed_work_on+0x4c/0x4c  \n  ? kthread_complete_and_exit+0x14/0x14  \n  ? ret_from_fork+0x24/0x38  \n  ? kthread_complete_and_exit+0x14/0x14  \n  ? ret_from_fork_asm+0xf/0x14  \n  ? entry_INT80_32+0xf0/0xf0  \n  \n[restore no-op path for no changes] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:06:48.000000Z"}, {"uuid": "40e70526-ffaa-499e-a585-7e1f3c17e322", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57898", "type": "seen", "source": "https://t.me/cvedetector/15445", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57898 - Linux Kernel wifi cfg80211 Link ID Information Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57898 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: cfg80211: clear link ID from bitmap during link delete after clean up  \n  \nCurrently, during link deletion, the link ID is first removed from the  \nvalid_links bitmap before performing any clean-up operations. However, some  \nfunctions require the link ID to remain in the valid_links bitmap. One  \nsuch example is cfg80211_cac_event(). The flow is -  \n  \nnl80211_remove_link()  \n    cfg80211_remove_link()  \n        ieee80211_del_intf_link()  \n            ieee80211_vif_set_links()  \n                ieee80211_vif_update_links()  \n                    ieee80211_link_stop()  \n                        cfg80211_cac_event()  \n  \ncfg80211_cac_event() requires link ID to be present but it is cleared  \nalready in cfg80211_remove_link(). Ultimately, WARN_ON() is hit.  \n  \nTherefore, clear the link ID from the bitmap only after completing the link  \nclean-up. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:06:47.000000Z"}, {"uuid": "0ba12088-c280-4fe3-8ff2-5d4007c707d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57897", "type": "seen", "source": "https://t.me/cvedetector/15443", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57897 - AMD KFD Linux Kernel DMA Direction Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57897 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/amdkfd: Correct the migration DMA map direction  \n  \nThe SVM DMA device map direction should be set the same as  \nthe DMA unmap setting, otherwise the DMA core will report  \nthe following warning.  \n  \nBefore finialize this solution, there're some discussion on  \nthe DMA mapping type(stream-based or coherent) in this KFD  \nmigration case, followed by   \n-45a1-4b88-86ee-fb0f35a0ca40@amd.com/T/.  \n  \nAs there's no dma_sync_single_for_*() in the DMA buffer accessed  \nthat because this migration operation should be sync properly and  \nautomatically. Give that there's might not be a performance problem  \nin various cache sync policy of DMA sync. Therefore, in order to  \nsimplify the DMA direction setting alignment, let's set the DMA map  \ndirection as BIDIRECTIONAL.  \n  \n[  150.834218] WARNING: CPU: 8 PID: 1812 at kernel/dma/debug.c:1028 check_unmap+0x1cc/0x930  \n[  150.834225] Modules linked in: amdgpu(OE) amdxcp drm_exec(OE) gpu_sched drm_buddy(OE) drm_ttm_helper(OE) ttm(OE) drm_suballoc_helper(OE) drm_display_helper(OE) drm_kms_helper(OE) i2c_algo_bit rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace netfs xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat xt_addrtype iptable_filter br_netfilter nvme_fabrics overlay nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge stp llc sch_fq_codel intel_rapl_msr amd_atl intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg edac_mce_amd snd_pci_acp6x snd_hda_codec snd_acp_config snd_hda_core snd_hwdep snd_soc_acpi kvm_amd sunrpc snd_pcm kvm binfmt_misc snd_seq_midi crct10dif_pclmul snd_seq_midi_event ghash_clmulni_intel sha512_ssse3 snd_rawmidi nls_iso8859_1 sha256_ssse3 sha1_ssse3 snd_seq aesni_intel snd_seq_device crypto_simd snd_timer cryptd input_leds  \n[  150.834310]  wmi_bmof serio_raw k10temp rapl snd sp5100_tco ipmi_devintf soundcore ccp ipmi_msghandler cm32181 industrialio mac_hid msr parport_pc ppdev lp parport efi_pstore drm(OE) ip_tables x_tables pci_stub crc32_pclmul nvme ahci libahci i2c_piix4 r8169 nvme_core i2c_designware_pci realtek i2c_ccgx_ucsi video wmi hid_generic cdc_ether usbnet usbhid hid r8152 mii  \n[  150.834354] CPU: 8 PID: 1812 Comm: rocrtst64 Tainted: G           OE      6.10.0-custom #492  \n[  150.834358] Hardware name: AMD Majolica-RN/Majolica-RN, BIOS RMJ1009A 06/13/2021  \n[  150.834360] RIP: 0010:check_unmap+0x1cc/0x930  \n[  150.834363] Code: c0 4c 89 4d c8 e8 34 bf 86 00 4c 8b 4d c8 4c 8b 45 c0 48 8b 4d b8 48 89 c6 41 57 4c 89 ea 48 c7 c7 80 49 b4 84 e8 b4 81 f3 ff <0f0b 48 c7 c7 04 83 ac 84 e8 76 ba fc ff 41 8b 76 4c 49 8d 7e 50  \n[  150.834365] RSP: 0018:ffffaac5023739e0 EFLAGS: 00010086  \n[  150.834368] RAX: 0000000000000000 RBX: ffffffff8566a2e0 RCX: 0000000000000027  \n[  150.834370] RDX: ffff8f6a8f621688 RSI: 0000000000000001 RDI: ffff8f6a8f621680  \n[  150.834372] RBP: ffffaac502373a30 R08: 00000000000000c9 R09: ffffaac502373850  \n[  150.834373] R10: ffffaac502373848 R11: ffffffff84f46328 R12: ffffaac502373a40  \n[  150.834375] R13: ffff8f6741045330 R14: ffff8f6741a77700 R15: ffffffff84ac831b  \n[  150.834377] FS:  00007faf0fc94c00(0000) GS:ffff8f6a8f600000(0000) knlGS:0000000000000000  \n[  150.834379] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \n[  150.834381] CR2: 00007faf0b600020 CR3: 000000010a52e000 CR4: 0000000000350ef0  \n[  150.834383] Call Trace:  \n[  150.834385]    \n[  150.834387]  ? show_regs+0x6d/0x80  \n[  150.834393]  ? __warn+0x8c/0x140  \n[  150.834397]  ? check_unmap+0x1cc/0x930  \n[  150.834400]  ? report_bug+0x193/0x1a0  \n[  150.834406]  ? handle_bug+0x46/0x80  \n[  150.834410]  ? exc_invalid_op+0x1d/0x80  \n[...]", "creation_timestamp": "2025-01-15T15:06:41.000000Z"}, {"uuid": "0a580e86-57a2-45ce-9148-48512a4e56bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57893", "type": "seen", "source": "https://t.me/cvedetector/15460", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57893 - ALSA OSS Linux Kernel Data Out-of-Bounds Access Vuln\", \n  \"Content\": \"CVE ID : CVE-2024-57893 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nALSA: seq: oss: Fix races at processing SysEx messages  \n  \nOSS sequencer handles the SysEx messages split in 6 bytes packets, and  \nALSA sequencer OSS layer tries to combine those.  It stores the data  \nin the internal buffer and this access is racy as of now, which may  \nlead to the out-of-bounds access.  \n  \nAs a temporary band-aid fix, introduce a mutex for serializing the  \nprocess of the SysEx message packets. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:40.000000Z"}, {"uuid": "2d98289e-52e7-4c90-af0a-5cfe6e8a9555", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "seen", "source": "https://t.me/cvedetector/15459", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57892 - Linux Kernel Ocfs2 Slab-Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57892 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv  \n  \nWhen mounting ocfs2 and then remounting it as read-only, a  \nslab-use-after-free occurs after the user uses a syscall to  \nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)->dqi_priv is the  \ndangling pointer.  \n  \nDuring the remounting process, the pointer dqi_priv is freed but is never  \nset as null leaving it to be accessed.  Additionally, the read-only option  \nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the  \nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the  \nnext quota, the function ocfs2_get_next_id is called and only checks the  \nquota usage flags and not the quota suspended flags.  \n  \nTo fix this, I set dqi_priv to null when it is freed after remounting with  \nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.  \n  \n[akpm@linux-foundation.org: coding-style cleanups] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:05.000000Z"}, {"uuid": "9955a59c-ec56-4175-bc9d-5b82b743bd25", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57891", "type": "seen", "source": "https://t.me/cvedetector/15458", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57891 - Linux Kernel - Unpredictable IRQ Restoration Vulnerability in Sched Ext\", \n  \"Content\": \"CVE ID : CVE-2024-57891 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsched_ext: Fix invalid irq restore in scx_ops_bypass()  \n  \nWhile adding outer irqsave/restore locking, 0e7ffff1b811 (\"scx: Fix raciness  \nin scx_ops_bypass()\") forgot to convert an inner rq_unlock_irqrestore() to  \nrq_unlock() which could re-enable IRQ prematurely leading to the following  \nwarning:  \n  \n  raw_local_irq_restore() called with IRQs enabled  \n  WARNING: CPU: 1 PID: 96 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40  \n  ...  \n  Sched_ext: create_dsq (enabling)  \n  pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)  \n  pc : warn_bogus_irq_restore+0x30/0x40  \n  lr : warn_bogus_irq_restore+0x30/0x40  \n  ...  \n  Call trace:  \n   warn_bogus_irq_restore+0x30/0x40 (P)  \n   warn_bogus_irq_restore+0x30/0x40 (L)  \n   scx_ops_bypass+0x224/0x3b8  \n   scx_ops_enable.isra.0+0x2c8/0xaa8  \n   bpf_scx_reg+0x18/0x30  \n  ...  \n  irq event stamp: 33739  \n  hardirqs last  enabled at (33739): [] scx_ops_bypass+0x174/0x3b8  \n  hardirqs last disabled at (33738): [] _raw_spin_lock_irqsave+0xb4/0xd8  \n  \nDrop the stray _irqrestore(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:04.000000Z"}, {"uuid": "09cfc369-f77a-453e-b2fc-a46863638bee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57890", "type": "seen", "source": "https://t.me/cvedetector/15457", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57890 - Linux Kernel RDMA/uverbs Integer Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57890 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRDMA/uverbs: Prevent integer overflow issue  \n  \nIn the expression \"cmd.wqe_size * cmd.wr_count\", both variables are u32  \nvalues that come from the user so the multiplication can lead to integer  \nwrapping.  Then we pass the result to uverbs_request_next_ptr() which also  \ncould potentially wrap.  The \"cmd.sge_count * sizeof(struct ib_uverbs_sge)\"  \nmultiplication can also overflow on 32bit systems although it's fine on  \n64bit systems.  \n  \nThis patch does two things.  First, I've re-arranged the condition in  \nuverbs_request_next_ptr() so that the use controlled variable \"len\" is on  \none side of the comparison by itself without any math.  Then I've modified  \nall the callers to use size_mul() for the multiplications. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:04.000000Z"}, {"uuid": "e4d050b0-906a-4a3d-a1f6-04d7fc65aff5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-5789", "type": "seen", "source": "https://t.me/cvedetector/5613", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-5789 - Stored Cross-Site Scripting vulnerability in WordPress Triton Lite theme Button shortcode.\", \n  \"Content\": \"CVE ID : CVE-2024-5789 \nPublished : Sept. 13, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : The Triton Lite theme for WordPress is vulnerable to Stored Cross-Site Scripting via the 'url' attribute within the theme's Button shortcode in all versions up to, and including, 1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. \nSeverity: 6.4 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"13 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-13T17:57:58.000000Z"}]}