https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 04 Jun 2026 05:05:45 +0000 https://db.gcve.eu/sighting/48f86443-6de2-4041-8c5c-4372335cecf7/export {"uuid": "48f86443-6de2-4041-8c5c-4372335cecf7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45012", "type": "seen", "source": "https://t.me/cvedetector/5381", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45012 - NVIDIA Nouveau Furious Firmware Fix\", \n \"Content\": \"CVE ID : CVE-2024-45012 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnouveau/firmware: use dma non-coherent allocator \n \nCurrently, enabling SG_DEBUG in the kernel will cause nouveau to hit a \nBUG() on startup, when the iommu is enabled: \n \nkernel BUG at include/linux/scatterlist.h:187! \ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI \nCPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 \nHardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 \nRIP: 0010:sg_init_one+0x85/0xa0 \nCode: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 \n24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 0b 0f 0b \n0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 \nRSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 \nRAX: 0000000000000000 RBX: ffffa77600d87000 RCX: 000000000000002b \nRDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa77680d87000 \nRBP: 000000000000e000 R08: 0000000000000000 R09: 0000000000000000 \nR10: ffff98f4c46aa508 R11: 0000000000000000 R12: ffff98f4c46aa508 \nR13: ffff98f4c46aa008 R14: ffffa77600d4a000 R15: ffffa77600d4a018 \nFS: 00007feeb5aae980(0000) GS:ffff98f5c4dc0000(0000) knlGS:0000000000000000 \nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \nCR2: 00007f22cb9a4520 CR3: 00000001043ba000 CR4: 00000000003506f0 \nCall Trace: \n \n ? die+0x36/0x90 \n ? do_trap+0xdd/0x100 \n ? sg_init_one+0x85/0xa0 \n ? do_error_trap+0x65/0x80 \n ? sg_init_one+0x85/0xa0 \n ? exc_invalid_op+0x50/0x70 \n ? sg_init_one+0x85/0xa0 \n ? asm_exc_invalid_op+0x1a/0x20 \n ? sg_init_one+0x85/0xa0 \n nvkm_firmware_ctor+0x14a/0x250 [nouveau] \n nvkm_falcon_fw_ctor+0x42/0x70 [nouveau] \n ga102_gsp_booter_ctor+0xb4/0x1a0 [nouveau] \n r535_gsp_oneinit+0xb3/0x15f0 [nouveau] \n ? srso_return_thunk+0x5/0x5f \n ? srso_return_thunk+0x5/0x5f \n ? nvkm_udevice_new+0x95/0x140 [nouveau] \n ? srso_return_thunk+0x5/0x5f \n ? srso_return_thunk+0x5/0x5f \n ? ktime_get+0x47/0xb0 \n \nFix this by using the non-coherent allocator instead, I think there \nmight be a better answer to this, but it involve ripping up some of \nAPIs using sg lists. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:41.000000Z"} {"uuid": "48f86443-6de2-4041-8c5c-4372335cecf7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45012", "type": "seen", "source": "https://t.me/cvedetector/5381", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45012 - NVIDIA Nouveau Furious Firmware Fix\", \n \"Content\": \"CVE ID : CVE-2024-45012 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnouveau/firmware: use dma non-coherent allocator \n \nCurrently, enabling SG_DEBUG in the kernel will cause nouveau to hit a \nBUG() on startup, when the iommu is enabled: \n \nkernel BUG at include/linux/scatterlist.h:187! \ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI \nCPU: 7 PID: 930 Comm: (udev-worker) Not tainted 6.9.0-rc3Lyude-Test+ #30 \nHardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019 \nRIP: 0010:sg_init_one+0x85/0xa0 \nCode: 69 88 32 01 83 e1 03 f6 c3 03 75 20 a8 01 75 1e 48 09 cb 41 89 54 \n24 08 49 89 1c 24 41 89 6c 24 0c 5b 5d 41 5c e9 7b b9 88 00 0b 0f 0b \n0f 0b 48 8b 05 5e 46 9a 01 eb b2 66 66 2e 0f 1f 84 00 \nRSP: 0018:ffffa776017bf6a0 EFLAGS: 00010246 \nRAX: 0000000000000000 RBX: ffffa77600d87000 RCX: 000000000000002b \nRDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffa77680d87000 \nRBP: 000000000000e000 R08: 0000000000000000 R09: 0000000000000000 \nR10: ffff98f4c46aa508 R11: 0000000000000000 R12: ffff98f4c46aa508 \nR13: ffff98f4c46aa008 R14: ffffa77600d4a000 R15: ffffa77600d4a018 \nFS: 00007feeb5aae980(0000) GS:ffff98f5c4dc0000(0000) knlGS:0000000000000000 \nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \nCR2: 00007f22cb9a4520 CR3: 00000001043ba000 CR4: 00000000003506f0 \nCall Trace: \n \n ? die+0x36/0x90 \n ? do_trap+0xdd/0x100 \n ? sg_init_one+0x85/0xa0 \n ? do_error_trap+0x65/0x80 \n ? sg_init_one+0x85/0xa0 \n ? exc_invalid_op+0x50/0x70 \n ? sg_init_one+0x85/0xa0 \n ? asm_exc_invalid_op+0x1a/0x20 \n ? sg_init_one+0x85/0xa0 \n nvkm_firmware_ctor+0x14a/0x250 [nouveau] \n nvkm_falcon_fw_ctor+0x42/0x70 [nouveau] \n ga102_gsp_booter_ctor+0xb4/0x1a0 [nouveau] \n r535_gsp_oneinit+0xb3/0x15f0 [nouveau] \n ? srso_return_thunk+0x5/0x5f \n ? srso_return_thunk+0x5/0x5f \n ? nvkm_udevice_new+0x95/0x140 [nouveau] \n ? srso_return_thunk+0x5/0x5f \n ? srso_return_thunk+0x5/0x5f \n ? ktime_get+0x47/0xb0 \n \nFix this by using the non-coherent allocator instead, I think there \nmight be a better answer to this, but it involve ripping up some of \nAPIs using sg lists. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:41.000000Z"} https://db.gcve.eu/sighting/48f86443-6de2-4041-8c5c-4372335cecf7/export Wed, 11 Sep 2024 18:41:41 +0000 https://db.gcve.eu/sighting/b1f51feb-9e04-4c64-964c-026a6af33cff/export {"uuid": "b1f51feb-9e04-4c64-964c-026a6af33cff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45019", "type": "seen", "source": "https://t.me/cvedetector/5383", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45019 - Intel Mellanox Ethernet Network Driver Multiple Lock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45019 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet/mlx5e: Take state lock during tx timeout reporter \n \nmlx5e_safe_reopen_channels() requires the state lock taken. The \nreferenced changed in the Fixes tag removed the lock to fix another \nissue. This patch adds it back but at a later point (when calling \nmlx5e_safe_reopen_channels()) to avoid the deadlock referenced in the \nFixes tag. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:42.000000Z"} {"uuid": "b1f51feb-9e04-4c64-964c-026a6af33cff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45019", "type": "seen", "source": "https://t.me/cvedetector/5383", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45019 - Intel Mellanox Ethernet Network Driver Multiple Lock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45019 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet/mlx5e: Take state lock during tx timeout reporter \n \nmlx5e_safe_reopen_channels() requires the state lock taken. The \nreferenced changed in the Fixes tag removed the lock to fix another \nissue. This patch adds it back but at a later point (when calling \nmlx5e_safe_reopen_channels()) to avoid the deadlock referenced in the \nFixes tag. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:42.000000Z"} https://db.gcve.eu/sighting/b1f51feb-9e04-4c64-964c-026a6af33cff/export Wed, 11 Sep 2024 18:41:42 +0000 https://db.gcve.eu/sighting/e30b02fa-8a07-4e67-8610-13daf2a3c18f/export {"uuid": "e30b02fa-8a07-4e67-8610-13daf2a3c18f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45018", "type": "seen", "source": "https://t.me/cvedetector/5382", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45018 - Linux Kernel Netfilter Flowtable Use After Free Buffer Overflow\", \n \"Content\": \"CVE ID : CVE-2024-45018 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetfilter: flowtable: initialise extack before use \n \nFix missing initialisation of extack in flow offload. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:42.000000Z"} {"uuid": "e30b02fa-8a07-4e67-8610-13daf2a3c18f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45018", "type": "seen", "source": "https://t.me/cvedetector/5382", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45018 - Linux Kernel Netfilter Flowtable Use After Free Buffer Overflow\", \n \"Content\": \"CVE ID : CVE-2024-45018 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetfilter: flowtable: initialise extack before use \n \nFix missing initialisation of extack in flow offload. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:42.000000Z"} https://db.gcve.eu/sighting/e30b02fa-8a07-4e67-8610-13daf2a3c18f/export Wed, 11 Sep 2024 18:41:42 +0000 https://db.gcve.eu/sighting/47848785-c105-4aaf-9d2b-9f69c38aa8f7/export {"uuid": "47848785-c105-4aaf-9d2b-9f69c38aa8f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45017", "type": "seen", "source": "https://t.me/cvedetector/5384", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45017 - Dell PowerEdge R7525 mlx5 IPsec RoCE MPV Trace Call Overflow Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45017 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet/mlx5: Fix IPsec RoCE MPV trace call \n \nPrevent the call trace below from happening, by not allowing IPsec \ncreation over a slave, if master device doesn't support IPsec. \n \nWARNING: CPU: 44 PID: 16136 at kernel/locking/rwsem.c:240 down_read+0x75/0x94 \nModules linked in: esp4_offload esp4 act_mirred act_vlan cls_flower sch_ingress mlx5_vdpa vringh vhost_iotlb vdpa mst_pciconf(OE) nfsv3 nfs_acl nfs lockd grace fscache netfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill cuse fuse rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_umad ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_ipoib iw_cm ib_cm ipmi_ssif intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul mlx5_ib ghash_clmulni_intel sha1_ssse3 dell_smbios ib_uverbs aesni_intel crypto_simd dcdbas wmi_bmof dell_wmi_descriptor cryptd pcspkr ib_core acpi_ipmi sp5100_tco ccp i2c_piix4 ipmi_si ptdma k10temp ipmi_devintf ipmi_msghandler acpi_power_meter acpi_cpufreq ext4 mbcache jbd2 sd_mod t10_pi sg mgag200 drm_kms_helper syscopyarea sysfillrect mlx5_core sysimgblt fb_sys_fops cec \n ahci libahci mlxfw drm pci_hyperv_intf libata tg3 sha256_ssse3 tls megaraid_sas i2c_algo_bit psample wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mst_pci] \nCPU: 44 PID: 16136 Comm: kworker/44:3 Kdump: loaded Tainted: GOE 5.15.0-20240509.el8uek.uek7_u3_update_v6.6_ipsec_bf.x86_64 #2 \nHardware name: Dell Inc. PowerEdge R7525/074H08, BIOS 2.0.3 01/15/2021 \nWorkqueue: events xfrm_state_gc_task \nRIP: 0010:down_read+0x75/0x94 \nCode: 00 48 8b 45 08 65 48 8b 14 25 80 fc 01 00 83 e0 02 48 09 d0 48 83 c8 01 48 89 45 08 5d 31 c0 89 c2 89 c6 89 c7 e9 cb 88 3b 00 0b 48 8b 45 08 a8 01 74 b2 a8 02 75 ae 48 89 c2 48 83 ca 02 f0 \nRSP: 0018:ffffb26387773da8 EFLAGS: 00010282 \nRAX: 0000000000000000 RBX: ffffa08b658af900 RCX: 0000000000000001 \nRDX: 0000000000000000 RSI: ff886bc5e1366f2f RDI: 0000000000000000 \nRBP: ffffa08b658af940 R08: 0000000000000000 R09: 0000000000000000 \nR10: 0000000000000000 R11: 0000000000000000 R12: ffffa0a9bfb31540 \nR13: ffffa0a9bfb37900 R14: 0000000000000000 R15: ffffa0a9bfb37905 \nFS: 0000000000000000(0000) GS:ffffa0a9bfb00000(0000) knlGS:0000000000000000 \nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \nCR2: 000055a45ed814e8 CR3: 000000109038a000 CR4: 0000000000350ee0 \nCall Trace: \n \n ? show_trace_log_lvl+0x1d6/0x2f9 \n ? show_trace_log_lvl+0x1d6/0x2f9 \n ? mlx5_devcom_for_each_peer_begin+0x29/0x60 [mlx5_core] \n ? down_read+0x75/0x94 \n ? __warn+0x80/0x113 \n ? down_read+0x75/0x94 \n ? report_bug+0xa4/0x11d \n ? handle_bug+0x35/0x8b \n ? exc_invalid_op+0x14/0x75 \n ? asm_exc_invalid_op+0x16/0x1b \n ? down_read+0x75/0x94 \n ? down_read+0xe/0x94 \n mlx5_devcom_for_each_peer_begin+0x29/0x60 [mlx5_core] \n mlx5_ipsec_fs_roce_tx_destroy+0xb1/0x130 [mlx5_core] \n tx_destroy+0x1b/0xc0 [mlx5_core] \n tx_ft_put+0x53/0xc0 [mlx5_core] \n mlx5e_xfrm_free_state+0x45/0x90 [mlx5_core] \n ___xfrm_state_destroy+0x10f/0x1a2 \n xfrm_state_gc_task+0x81/0xa9 \n process_one_work+0x1f1/0x3c6 \n worker_thread+0x53/0x3e4 \n ? process_one_work.cold+0x46/0x3c \n kthread+0x127/0x144 \n ? set_kthread_struct+0x60/0x52 \n ret_from_fork+0x22/0x2d \n \n---[ end trace 5ef7896144d398e1 ]--- \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:43.000000Z"} {"uuid": "47848785-c105-4aaf-9d2b-9f69c38aa8f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45017", "type": "seen", "source": "https://t.me/cvedetector/5384", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45017 - Dell PowerEdge R7525 mlx5 IPsec RoCE MPV Trace Call Overflow Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45017 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet/mlx5: Fix IPsec RoCE MPV trace call \n \nPrevent the call trace below from happening, by not allowing IPsec \ncreation over a slave, if master device doesn't support IPsec. \n \nWARNING: CPU: 44 PID: 16136 at kernel/locking/rwsem.c:240 down_read+0x75/0x94 \nModules linked in: esp4_offload esp4 act_mirred act_vlan cls_flower sch_ingress mlx5_vdpa vringh vhost_iotlb vdpa mst_pciconf(OE) nfsv3 nfs_acl nfs lockd grace fscache netfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill cuse fuse rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_core_mod ib_umad ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_ipoib iw_cm ib_cm ipmi_ssif intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul mlx5_ib ghash_clmulni_intel sha1_ssse3 dell_smbios ib_uverbs aesni_intel crypto_simd dcdbas wmi_bmof dell_wmi_descriptor cryptd pcspkr ib_core acpi_ipmi sp5100_tco ccp i2c_piix4 ipmi_si ptdma k10temp ipmi_devintf ipmi_msghandler acpi_power_meter acpi_cpufreq ext4 mbcache jbd2 sd_mod t10_pi sg mgag200 drm_kms_helper syscopyarea sysfillrect mlx5_core sysimgblt fb_sys_fops cec \n ahci libahci mlxfw drm pci_hyperv_intf libata tg3 sha256_ssse3 tls megaraid_sas i2c_algo_bit psample wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mst_pci] \nCPU: 44 PID: 16136 Comm: kworker/44:3 Kdump: loaded Tainted: GOE 5.15.0-20240509.el8uek.uek7_u3_update_v6.6_ipsec_bf.x86_64 #2 \nHardware name: Dell Inc. PowerEdge R7525/074H08, BIOS 2.0.3 01/15/2021 \nWorkqueue: events xfrm_state_gc_task \nRIP: 0010:down_read+0x75/0x94 \nCode: 00 48 8b 45 08 65 48 8b 14 25 80 fc 01 00 83 e0 02 48 09 d0 48 83 c8 01 48 89 45 08 5d 31 c0 89 c2 89 c6 89 c7 e9 cb 88 3b 00 0b 48 8b 45 08 a8 01 74 b2 a8 02 75 ae 48 89 c2 48 83 ca 02 f0 \nRSP: 0018:ffffb26387773da8 EFLAGS: 00010282 \nRAX: 0000000000000000 RBX: ffffa08b658af900 RCX: 0000000000000001 \nRDX: 0000000000000000 RSI: ff886bc5e1366f2f RDI: 0000000000000000 \nRBP: ffffa08b658af940 R08: 0000000000000000 R09: 0000000000000000 \nR10: 0000000000000000 R11: 0000000000000000 R12: ffffa0a9bfb31540 \nR13: ffffa0a9bfb37900 R14: 0000000000000000 R15: ffffa0a9bfb37905 \nFS: 0000000000000000(0000) GS:ffffa0a9bfb00000(0000) knlGS:0000000000000000 \nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 \nCR2: 000055a45ed814e8 CR3: 000000109038a000 CR4: 0000000000350ee0 \nCall Trace: \n \n ? show_trace_log_lvl+0x1d6/0x2f9 \n ? show_trace_log_lvl+0x1d6/0x2f9 \n ? mlx5_devcom_for_each_peer_begin+0x29/0x60 [mlx5_core] \n ? down_read+0x75/0x94 \n ? __warn+0x80/0x113 \n ? down_read+0x75/0x94 \n ? report_bug+0xa4/0x11d \n ? handle_bug+0x35/0x8b \n ? exc_invalid_op+0x14/0x75 \n ? asm_exc_invalid_op+0x16/0x1b \n ? down_read+0x75/0x94 \n ? down_read+0xe/0x94 \n mlx5_devcom_for_each_peer_begin+0x29/0x60 [mlx5_core] \n mlx5_ipsec_fs_roce_tx_destroy+0xb1/0x130 [mlx5_core] \n tx_destroy+0x1b/0xc0 [mlx5_core] \n tx_ft_put+0x53/0xc0 [mlx5_core] \n mlx5e_xfrm_free_state+0x45/0x90 [mlx5_core] \n ___xfrm_state_destroy+0x10f/0x1a2 \n xfrm_state_gc_task+0x81/0xa9 \n process_one_work+0x1f1/0x3c6 \n worker_thread+0x53/0x3e4 \n ? process_one_work.cold+0x46/0x3c \n kthread+0x127/0x144 \n ? set_kthread_struct+0x60/0x52 \n ret_from_fork+0x22/0x2d \n \n---[ end trace 5ef7896144d398e1 ]--- \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:43.000000Z"} https://db.gcve.eu/sighting/47848785-c105-4aaf-9d2b-9f69c38aa8f7/export Wed, 11 Sep 2024 18:41:43 +0000 https://db.gcve.eu/sighting/41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9/export {"uuid": "41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://t.me/cvedetector/5385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45010 - Linux MPTCP Local Address Used Counter Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45010 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: pm: only mark 'subflow' endp as available \n \nAdding the following warning ... \n \n WARN_ON_ONCE(msk->pm.local_addr_used == 0) \n \n... before decrementing the local_addr_used counter helped to find a bug \nwhen running the \"remove single address\" subtest from the mptcp_join.sh \nselftests. \n \nRemoving a 'signal' endpoint will trigger the removal of all subflows \nlinked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with \nrm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used \ncounter, which is wrong in this case because this counter is linked to \n'subflow' endpoints, and here it is a 'signal' endpoint that is being \nremoved. \n \nNow, the counter is decremented, only if the ID is being used outside \nof mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and \nif the ID is not 0 -- local_addr_used is not taking into account these \nones. This marking of the ID as being available, and the decrement is \ndone no matter if a subflow using this ID is currently available, \nbecause the subflow could have been closed before. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:44.000000Z"} {"uuid": "41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://t.me/cvedetector/5385", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45010 - Linux MPTCP Local Address Used Counter Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45010 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmptcp: pm: only mark 'subflow' endp as available \n \nAdding the following warning ... \n \n WARN_ON_ONCE(msk->pm.local_addr_used == 0) \n \n... before decrementing the local_addr_used counter helped to find a bug \nwhen running the \"remove single address\" subtest from the mptcp_join.sh \nselftests. \n \nRemoving a 'signal' endpoint will trigger the removal of all subflows \nlinked to this endpoint via mptcp_pm_nl_rm_addr_or_subflow() with \nrm_type == MPTCP_MIB_RMSUBFLOW. This will decrement the local_addr_used \ncounter, which is wrong in this case because this counter is linked to \n'subflow' endpoints, and here it is a 'signal' endpoint that is being \nremoved. \n \nNow, the counter is decremented, only if the ID is being used outside \nof mptcp_pm_nl_rm_addr_or_subflow(), only for 'subflow' endpoints, and \nif the ID is not 0 -- local_addr_used is not taking into account these \nones. This marking of the ID as being available, and the decrement is \ndone no matter if a subflow using this ID is currently available, \nbecause the subflow could have been closed before. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:41:44.000000Z"} https://db.gcve.eu/sighting/41d7d766-6d70-46dd-9e7d-a7c2b23a8bd9/export Wed, 11 Sep 2024 18:41:44 +0000 https://db.gcve.eu/sighting/6e7d6127-d5e2-4478-8f12-901b5b341268/export {"uuid": "6e7d6127-d5e2-4478-8f12-901b5b341268", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45016", "type": "seen", "source": "https://t.me/cvedetector/5386", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45016 - Linux kernel Netem Use-After-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45016 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetem: fix return value if duplicate enqueue fails \n \nThere is a bug in netem_enqueue() introduced by \ncommit 5845f706388a (\"net: netem: fix skb length BUG_ON in __skb_to_sgvec\") \nthat can lead to a use-after-free. \n \nThis commit made netem_enqueue() always return NET_XMIT_SUCCESS \nwhen a packet is duplicated, which can cause the parent qdisc's q.qlen \nto be mistakenly incremented. When this happens qlen_notify() may be \nskipped on the parent during destruction, leaving a dangling pointer \nfor some classful qdiscs like DRR. \n \nThere are two ways for the bug happen: \n \n- If the duplicated packet is dropped by rootq->enqueue() and then \n the original packet is also dropped. \n- If rootq->enqueue() sends the duplicated packet to a different qdisc \n and the original packet is dropped. \n \nIn both cases NET_XMIT_SUCCESS is returned even though no packets \nare enqueued at the netem qdisc. \n \nThe fix is to defer the enqueue of the duplicate packet until after \nthe original packet has been guaranteed to return NET_XMIT_SUCCESS. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:42:20.000000Z"} {"uuid": "6e7d6127-d5e2-4478-8f12-901b5b341268", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45016", "type": "seen", "source": "https://t.me/cvedetector/5386", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-45016 - Linux kernel Netem Use-After-Free Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-45016 \nPublished : Sept. 11, 2024, 4:15 p.m. | 16\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnetem: fix return value if duplicate enqueue fails \n \nThere is a bug in netem_enqueue() introduced by \ncommit 5845f706388a (\"net: netem: fix skb length BUG_ON in __skb_to_sgvec\") \nthat can lead to a use-after-free. \n \nThis commit made netem_enqueue() always return NET_XMIT_SUCCESS \nwhen a packet is duplicated, which can cause the parent qdisc's q.qlen \nto be mistakenly incremented. When this happens qlen_notify() may be \nskipped on the parent during destruction, leaving a dangling pointer \nfor some classful qdiscs like DRR. \n \nThere are two ways for the bug happen: \n \n- If the duplicated packet is dropped by rootq->enqueue() and then \n the original packet is also dropped. \n- If rootq->enqueue() sends the duplicated packet to a different qdisc \n and the original packet is dropped. \n \nIn both cases NET_XMIT_SUCCESS is returned even though no packets \nare enqueued at the netem qdisc. \n \nThe fix is to defer the enqueue of the duplicate packet until after \nthe original packet has been guaranteed to return NET_XMIT_SUCCESS. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"11 Sep 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-11T18:42:20.000000Z"} https://db.gcve.eu/sighting/6e7d6127-d5e2-4478-8f12-901b5b341268/export Wed, 11 Sep 2024 18:42:20 +0000 https://db.gcve.eu/sighting/de75ea80-1925-4a31-962a-f1704c0b70bd/export {"uuid": "de75ea80-1925-4a31-962a-f1704c0b70bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45015", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} {"uuid": "de75ea80-1925-4a31-962a-f1704c0b70bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-45015", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"} https://db.gcve.eu/sighting/de75ea80-1925-4a31-962a-f1704c0b70bd/export Wed, 03 Dec 2025 14:14:49 +0000 https://db.gcve.eu/sighting/54a3f609-8875-4141-92a9-8e864d72095a/export {"uuid": "54a3f609-8875-4141-92a9-8e864d72095a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "54a3f609-8875-4141-92a9-8e864d72095a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-45010", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://db.gcve.eu/sighting/54a3f609-8875-4141-92a9-8e864d72095a/export Thu, 19 Mar 2026 00:00:00 +0000 https://db.gcve.eu/sighting/2f4d84b5-5dd9-410e-8ffd-edf48f21453e/export {"uuid": "2f4d84b5-5dd9-410e-8ffd-edf48f21453e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-45015", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} {"uuid": "2f4d84b5-5dd9-410e-8ffd-edf48f21453e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-45015", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"} https://db.gcve.eu/sighting/2f4d84b5-5dd9-410e-8ffd-edf48f21453e/export Thu, 19 Mar 2026 00:00:00 +0000