{"vulnerability": "CVE-2024-5665", "sightings": [{"uuid": "9083643a-870f-4720-b11a-e2fce488d541", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56656", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzszol62a", "content": "", "creation_timestamp": "2024-12-27T15:20:21.155040Z"}, {"uuid": "4ee9b696-28b3-4e6c-9f36-db9b0fb7aa14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56655", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzqxdsz2m", "content": "", "creation_timestamp": "2024-12-27T15:20:18.907798Z"}, {"uuid": "e477cd05-73b0-4893-9be9-31d7e6cdfdee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56659", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecc22einf2k", "content": "", "creation_timestamp": "2024-12-27T15:20:28.731075Z"}, {"uuid": "9d2858c2-2fd6-4904-b69c-6733f557b66e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56650", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzcxysm2c", "content": "", "creation_timestamp": "2024-12-27T15:20:04.107703Z"}, {"uuid": "ad2a0173-039c-4c83-8197-066b7e30a3a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56651", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzfmltm2c", "content": "", "creation_timestamp": "2024-12-27T15:20:06.918790Z"}, {"uuid": "9ea5b64a-d9c4-4403-a861-5503e10f6618", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56652", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzi45qe2c", "content": "", "creation_timestamp": "2024-12-27T15:20:09.448000Z"}, {"uuid": "20abe350-a5e6-4c09-a51e-a0df9fe9dfeb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56653", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzlluyb25", "content": "", "creation_timestamp": "2024-12-27T15:20:13.513350Z"}, {"uuid": "0a46e5ad-8baa-4a30-9c1b-0085f9f594ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzohx3e2e", "content": "", "creation_timestamp": "2024-12-27T15:20:16.415258Z"}, {"uuid": "cda045ae-701a-48c7-a673-355d2b546621", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56657", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzvk2ve25", "content": "", "creation_timestamp": "2024-12-27T15:20:23.862814Z"}, {"uuid": "9564252e-7a98-4c40-90ea-f24dfa6a2b44", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56658", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzxyqj322", "content": "", "creation_timestamp": "2024-12-27T15:20:26.588543Z"}, {"uuid": "e79cb41d-c2ad-411b-872e-8f15bc6be288", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56659", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113725888571599763", "content": "", "creation_timestamp": "2024-12-27T17:09:05.520992Z"}, {"uuid": "9422f6a5-8cd2-4686-b4ee-a0dd35d43f7a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56652", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113725941584643019", "content": "", "creation_timestamp": "2024-12-27T17:22:33.961040Z"}, {"uuid": "08ad3d1e-9dfa-412d-9e92-bd01d6047440", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56659", "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": "4d285dbd-d881-481a-afef-362486be3e9f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56658", "type": "seen", "source": "https://bsky.app/profile/gcpweekly.bsky.social/post/3lwhluqui2w2q", "content": "", "creation_timestamp": "2025-08-15T19:33:05.565807Z"}, {"uuid": "c2068762-3793-4f3c-a15c-7f2832024cb7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56651", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "64622f04-17b3-4611-bffc-d78d0295c837", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56652", "type": "seen", "source": "https://t.me/cvedetector/13777", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56652 - Linux XE drm slab use-after-free vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56652 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/xe/reg_sr: Remove register pool  \n  \nThat pool implementation doesn't really work: if the krealloc happens to  \nmove the memory and return another address, the entries in the xarray  \nbecome invalid, leading to use-after-free later:  \n  \n BUG: KASAN: slab-use-after-free in xe_reg_sr_apply_mmio+0x570/0x760 [xe]  \n Read of size 4 at addr ffff8881244b2590 by task modprobe/2753  \n  \n Allocated by task 2753:  \n  kasan_save_stack+0x39/0x70  \n  kasan_save_track+0x14/0x40  \n  kasan_save_alloc_info+0x37/0x60  \n  __kasan_kmalloc+0xc3/0xd0  \n  __kmalloc_node_track_caller_noprof+0x200/0x6d0  \n  krealloc_noprof+0x229/0x380  \n  \nSimplify the code to fix the bug. A better pooling strategy may be added  \nback later if needed.  \n  \n(cherry picked from commit e5283bd4dfecbd3335f43b62a68e24dae23f59e4) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:11.000000Z"}, {"uuid": "ee621cf4-73e5-4fa6-90ca-371fcc0d8828", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56658", "type": "seen", "source": "https://gist.github.com/webmutation/894dd1a9a17615b7469198bb18bc3a16", "content": "", "creation_timestamp": "2025-04-12T00:10:16.000000Z"}, {"uuid": "396d91d3-51a7-43de-b3d9-5b0e79e29e69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56650", "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": "589b531a-2263-4ac6-9032-3c2f5919c2cc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-56657", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "2c02feef-3870-48e4-a823-de8aec57f62b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-5665", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/168", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: GHSA-ppp3-73jm-5rm6\n\ud83d\udd17 Aliases: CVE-2024-56675\n\ud83d\udd39 Details: In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors\n\nUprobes always use bpf_prog_run_array_uprobe() under tasks-trace-RCU\nprotection. But it is possible to attach a non-sleepable BPF program to a\nuprobe, and non-sleepable BPF programs are freed via normal RCU (see\n__bpf_prog_put_noref()). This leads to UAF of the bpf_prog because a normal\nRCU grace period does not imply a tasks-trace-RCU grace period.\n\nFix it by explicitly waiting for a tasks-trace-RCU grace period after\nremoving the attachment of a bpf_prog to a perf_event.\n\ud83d\udd22 Severity: CVSS_V3: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\n\ud83d\uddd3\ufe0f Modified: 2025-01-06T15:30:59Z\n\ud83d\uddd3\ufe0f Published: 2024-12-27T15:31:56Z\n\ud83c\udff7\ufe0f CWE IDs: CWE-416\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2024-5665\n2. https://git.kernel.org/stable/c/9245459a992d22fe0e92e988f49db1fec82c184a\n3. https://git.kernel.org/stable/c/9b53d2c2a38a1effc341d99be3f99faef104d\n4. https://git.kernel.org/stable/c/ef1b808e3bc98612feceedf985c2fbbeb28f956\n5. https://git.kernel.org/stable/c/f9f85df30118f3f411261e6682fc60ebcce23e5", "creation_timestamp": "2025-01-06T15:37:11.000000Z"}, {"uuid": "eeb8d03b-e68d-457b-b909-3811dec73fbd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56653", "type": "seen", "source": "https://t.me/cvedetector/13779", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56653 - Bluetooth btusb UAF\", \n  \"Content\": \"CVE ID : CVE-2024-56653 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: btmtk: avoid UAF in btmtk_process_coredump  \n  \nhci_devcd_append may lead to the release of the skb, so it cannot be  \naccessed once it is called.  \n  \n==================================================================  \nBUG: KASAN: slab-use-after-free in btmtk_process_coredump+0x2a7/0x2d0 [btmtk]  \nRead of size 4 at addr ffff888033cfabb0 by task kworker/0:3/82  \n  \nCPU: 0 PID: 82 Comm: kworker/0:3 Tainted: G     U             6.6.40-lockdep-03464-g1d8b4eb3060e #1 b0b3c1cc0c842735643fb411799d97921d1f688c  \nHardware name: Google Yaviks_Ufs/Yaviks_Ufs, BIOS Google_Yaviks_Ufs.15217.552.0 05/07/2024  \nWorkqueue: events btusb_rx_work [btusb]  \nCall Trace:  \n   \n dump_stack_lvl+0xfd/0x150  \n print_report+0x131/0x780  \n kasan_report+0x177/0x1c0  \n btmtk_process_coredump+0x2a7/0x2d0 [btmtk 03edd567dd71a65958807c95a65db31d433e1d01]  \n btusb_recv_acl_mtk+0x11c/0x1a0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec]  \n btusb_rx_work+0x9e/0xe0 [btusb 675430d1e87c4f24d0c1f80efe600757a0f32bec]  \n worker_thread+0xe44/0x2cc0  \n kthread+0x2ff/0x3a0  \n ret_from_fork+0x51/0x80  \n ret_from_fork_asm+0x1b/0x30  \n   \n  \nAllocated by task 82:  \n stack_trace_save+0xdc/0x190  \n kasan_set_track+0x4e/0x80  \n __kasan_slab_alloc+0x4e/0x60  \n kmem_cache_alloc+0x19f/0x360  \n skb_clone+0x132/0xf70  \n btusb_recv_acl_mtk+0x104/0x1a0 [btusb]  \n btusb_rx_work+0x9e/0xe0 [btusb]  \n worker_thread+0xe44/0x2cc0  \n kthread+0x2ff/0x3a0  \n ret_from_fork+0x51/0x80  \n ret_from_fork_asm+0x1b/0x30  \n  \nFreed by task 1733:  \n stack_trace_save+0xdc/0x190  \n kasan_set_track+0x4e/0x80  \n kasan_save_free_info+0x28/0xb0  \n ____kasan_slab_free+0xfd/0x170  \n kmem_cache_free+0x183/0x3f0  \n hci_devcd_rx+0x91a/0x2060 [bluetooth]  \n worker_thread+0xe44/0x2cc0  \n kthread+0x2ff/0x3a0  \n ret_from_fork+0x51/0x80  \n ret_from_fork_asm+0x1b/0x30  \n  \nThe buggy address belongs to the object at ffff888033cfab40  \n which belongs to the cache skbuff_head_cache of size 232  \nThe buggy address is located 112 bytes inside of  \n freed 232-byte region [ffff888033cfab40, ffff888033cfac28)  \n  \nThe buggy address belongs to the physical page:  \npage:00000000a174ba93 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x33cfa  \nhead:00000000a174ba93 order:1 entire_mapcount:0 nr_pages_mapped:0 pincount:0  \nanon flags: 0x4000000000000840(slab|head|zone=1)  \npage_type: 0xffffffff()  \nraw: 4000000000000840 ffff888100848a00 0000000000000000 0000000000000001  \nraw: 0000000000000000 0000000080190019 00000001ffffffff 0000000000000000  \npage dumped because: kasan: bad access detected  \n  \nMemory state around the buggy address:  \n ffff888033cfaa80: fb fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc  \n ffff888033cfab00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb  \n>ffff888033cfab80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb  \n                                     ^  \n ffff888033cfac00: fb fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc  \n ffff888033cfac80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb  \n==================================================================  \n  \nCheck if we need to call hci_devcd_complete before calling  \nhci_devcd_append. That requires that we check data->cd_info.cnt >=  \nMTK_COREDUMP_NUM instead of data->cd_info.cnt > MTK_COREDUMP_NUM, as we  \nincrement data->cd_info.cnt only once the call to hci_devcd_append  \nsucceeds. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:13.000000Z"}, {"uuid": "77aac787-7f49-4d3c-8057-820c82cde33f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://t.me/cvedetector/13778", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56654 - Linux Bluetooth RCU List Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56654 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: hci_event: Fix using rcu_read_(un)lock while iterating  \n  \nThe usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is  \nnot safe since for the most part entries fetched this way shall be  \ntreated as rcu_dereference:  \n  \n Note that the value returned by rcu_dereference() is valid  \n only within the enclosing RCU read-side critical section [1]_.  \n For example, the following is **not** legal::  \n  \n  rcu_read_lock();  \n  p = rcu_dereference(head.next);  \n  rcu_read_unlock();  \n  x = p->address; /* BUG!!! */  \n  rcu_read_lock();  \n  y = p->data; /* BUG!!! */  \n  rcu_read_unlock(); \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:12.000000Z"}, {"uuid": "2d0dae7f-4b97-48e7-b863-dcbc5c5c7810", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56658", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "17ec1aea-287c-4dc0-848e-357bd5c4af8e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56656", "type": "seen", "source": "https://t.me/cvedetector/13780", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56656 - Dell PowerEdge R760 bnxt_en Aggregation ID Mask Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56656 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbnxt_en: Fix aggregation ID mask to prevent oops on 5760X chips  \n  \nThe 5760X (P7) chip's HW GRO/LRO interface is very similar to that of  \nthe previous generation (5750X or P5).  However, the aggregation ID  \nfields in the completion structures on P7 have been redefined from  \n16 bits to 12 bits.  The freed up 4 bits are redefined for part of the  \nmetadata such as the VLAN ID.  The aggregation ID mask was not modified  \nwhen adding support for P7 chips.  Including the extra 4 bits for the  \naggregation ID can potentially cause the driver to store or fetch the  \npacket header of GRO/LRO packets in the wrong TPA buffer.  It may hit  \nthe BUG() condition in __skb_pull() because the SKB contains no valid  \npacket header:  \n  \nkernel BUG at include/linux/skbuff.h:2766!  \nOops: invalid opcode: 0000 1 PREEMPT SMP NOPTI  \nCPU: 4 UID: 0 PID: 0 Comm: swapper/4 Kdump: loaded Tainted: G           OE      6.12.0-rc2+ #7  \nTainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  \nHardware name: Dell Inc. PowerEdge R760/0VRV9X, BIOS 1.0.1 12/27/2022  \nRIP: 0010:eth_type_trans+0xda/0x140  \nCode: 80 00 00 00 eb c1 8b 47 70 2b 47 74 48 8b 97 d0 00 00 00 83 f8 01 7e 1b 48 85 d2 74 06 66 83 3a ff 74 09 b8 00 04 00 00 eb a5 <0f0b b8 00 01 00 00 eb 9c 48 85 ff 74 eb 31 f6 b9 02 00 00 00 48  \nRSP: 0018:ff615003803fcc28 EFLAGS: 00010283  \nRAX: 00000000000022d2 RBX: 0000000000000003 RCX: ff2e8c25da334040  \nRDX: 0000000000000040 RSI: ff2e8c25c1ce8000 RDI: ff2e8c25869f9000  \nRBP: ff2e8c258c31c000 R08: ff2e8c25da334000 R09: 0000000000000001  \nR10: ff2e8c25da3342c0 R11: ff2e8c25c1ce89c0 R12: ff2e8c258e0990b0  \nR13: ff2e8c25bb120000 R14: ff2e8c25c1ce89c0 R15: ff2e8c25869f9000  \nFS:  0000000000000000(0000) GS:ff2e8c34be300000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 000055f05317e4c8 CR3: 000000108bac6006 CR4: 0000000000773ef0  \nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000  \nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400  \nPKRU: 55555554  \nCall Trace:  \n   \n ? die+0x33/0x90  \n ? do_trap+0xd9/0x100  \n ? eth_type_trans+0xda/0x140  \n ? do_error_trap+0x65/0x80  \n ? eth_type_trans+0xda/0x140  \n ? exc_invalid_op+0x4e/0x70  \n ? eth_type_trans+0xda/0x140  \n ? asm_exc_invalid_op+0x16/0x20  \n ? eth_type_trans+0xda/0x140  \n bnxt_tpa_end+0x10b/0x6b0 [bnxt_en]  \n ? bnxt_tpa_start+0x195/0x320 [bnxt_en]  \n bnxt_rx_pkt+0x902/0xd90 [bnxt_en]  \n ? __bnxt_tx_int.constprop.0+0x89/0x300 [bnxt_en]  \n ? kmem_cache_free+0x343/0x440  \n ? __bnxt_tx_int.constprop.0+0x24f/0x300 [bnxt_en]  \n __bnxt_poll_work+0x193/0x370 [bnxt_en]  \n bnxt_poll_p5+0x9a/0x300 [bnxt_en]  \n ? try_to_wake_up+0x209/0x670  \n __napi_poll+0x29/0x1b0  \n  \nFix it by redefining the aggregation ID mask for P5_PLUS chips to be  \n12 bits.  This will work because the maximum aggregation ID is less  \nthan 4096 on all P5_PLUS chips. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:14.000000Z"}, {"uuid": "c538c626-9f96-4744-a3bd-d27faeae37b3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56657", "type": "seen", "source": "https://t.me/cvedetector/13782", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56657 - Alsa Linux Kernel Symlink Error Information Disclosure\", \n  \"Content\": \"CVE ID : CVE-2024-56657 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nALSA: control: Avoid WARN() for symlink errors  \n  \nUsing WARN() for showing the error of symlink creations don't give  \nmore information than telling that something goes wrong, since the  \nusual code path is a lregister callback from each control element  \ncreation.  More badly, the use of WARN() rather confuses fuzzer as if  \nit were serious issues.  \n  \nThis patch downgrades the warning messages to use the normal dev_err()  \ninstead of WARN().  For making it clearer, add the function name to  \nthe prefix, too. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:51.000000Z"}, {"uuid": "4ccc9062-14a2-4352-a9f1-3ac3c153968c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56655", "type": "seen", "source": "https://t.me/cvedetector/13781", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56655 - Linux Kernel Netfilter NF_Tables RCU Race Condition Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56655 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nf_tables: do not defer rule destruction via call_rcu  \n  \nnf_tables_chain_destroy can sleep, it can't be used from call_rcu  \ncallbacks.  \n  \nMoreover, nf_tables_rule_release() is only safe for error unwinding,  \nwhile transaction mutex is held and the to-be-desroyed rule was not  \nexposed to either dataplane or dumps, as it deactives+frees without  \nthe required synchronize_rcu() in-between.  \n  \nnft_rule_expr_deactivate() callbacks will change ->use counters  \nof other chains/sets, see e.g. nft_lookup .deactivate callback, these  \nmust be serialized via transaction mutex.  \n  \nAlso add a few lockdep asserts to make this more explicit.  \n  \nCalling synchronize_rcu() isn't ideal, but fixing this without is hard  \nand way more intrusive.  As-is, we can get:  \n  \nWARNING: .. net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x..  \nWorkqueue: events nf_tables_trans_destroy_work  \nRIP: 0010:nft_set_destroy+0x3fe/0x5c0  \nCall Trace:  \n   \n nf_tables_trans_destroy_work+0x6b7/0xad0  \n process_one_work+0x64a/0xce0  \n worker_thread+0x613/0x10d0  \n  \nIn case the synchronize_rcu becomes an issue, we can explore alternatives.  \n  \nOne way would be to allocate nft_trans_rule objects + one nft_trans_chain  \nobject, deactivate the rules + the chain and then defer the freeing to the  \nnft destroy workqueue.  We'd still need to keep the synchronize_rcu path as  \na fallback to handle -ENOMEM corner cases though. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:51.000000Z"}]}