{"vulnerability": "CVE-2024-4384", "sightings": [{"uuid": "c24d49d6-8b86-49bc-9fc7-9353206325b7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-43842", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "67a9bf0e-7fc6-4f62-857c-ad3add902700", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-43844", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "3d610b25-fd55-4ee3-950b-f7dcbd7a5ed3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43849", "type": "seen", "source": "https://t.me/cvedetector/3421", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43849 - Qualcomm qcom Soc Memory Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43849 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nsoc: qcom: pdr: protect locator_addr with the main mutex  \n  \nIf the service locator server is restarted fast enough, the PDR can  \nrewrite locator_addr fields concurrently. Protect them by placing  \nmodification of those fields under the main pdr->lock. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:16.000000Z"}, {"uuid": "adb2d5fc-bd7c-4307-bcc8-9224d91fb85f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43847", "type": "seen", "source": "https://t.me/cvedetector/3429", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43847 - Linux Ath12k WiFi Invalid Memory Access Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43847 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: ath12k: fix invalid memory access while processing fragmented packets  \n  \nThe monitor ring and the reo reinject ring share the same ring mask index.  \nWhen the driver receives an interrupt for the reo reinject ring, the  \nmonitor ring is also processed, leading to invalid memory access. Since  \nmonitor support is not yet enabled in ath12k, the ring mask for the monitor  \nring should be removed.  \n  \nTested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.1.1-00209-QCAHKSWPL_SILICONZ-1 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:24.000000Z"}, {"uuid": "18852568-6eb6-4576-85c3-6bbad09c35af", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43845", "type": "seen", "source": "https://t.me/cvedetector/3428", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43845 - Linux udft Uninitialized Memory Access\", \n  \"Content\": \"CVE ID : CVE-2024-43845 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nudf: Fix bogus checksum computation in udf_rename()  \n  \nSyzbot reports uninitialized memory access in udf_rename() when updating  \nchecksum of '..' directory entry of a moved directory. This is indeed  \ntrue as we pass on-stack diriter.fi to the udf_update_tag() and because  \nthat has only struct fileIdentDesc included in it and not the impUse or  \nname fields, the checksumming function is going to checksum random stack  \ncontents beyond the end of the structure. This is actually harmless  \nbecause the following udf_fiiter_write_fi() will recompute the checksum  \nfrom on-disk buffers where everything is properly included. So all that  \nis needed is just removing the bogus calculation. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:23.000000Z"}, {"uuid": "88c895fc-5f9f-4457-b3d5-71147dda6ca7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43844", "type": "seen", "source": "https://t.me/cvedetector/3430", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43844 - HP Meep Wireless_bug Offload Handler Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43844 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: rtw89: wow: fix GTK offload H2C skbuff issue  \n  \nWe mistakenly put skb too large and that may exceed skb->end.  \nTherefore, we fix it.  \n  \nskbuff: skb_over_panic: text:ffffffffc09e9a9d len:416 put:204 head:ffff8fba04eca780 data:ffff8fba04eca7e0 tail:0x200 end:0x140 dev:  \n------------[ cut here ]------------  \nkernel BUG at net/core/skbuff.c:192!  \ninvalid opcode: 0000 [#1] PREEMPT SMP PTI  \nCPU: 1 PID: 4747 Comm: kworker/u4:44 Tainted: G           O       6.6.30-02659-gc18865c4dfbd #1 86547039b47e46935493f615ee31d0b2d711d35e  \nHardware name: HP Meep/Meep, BIOS Google_Meep.11297.262.0 03/18/2021  \nWorkqueue: events_unbound async_run_entry_fn  \nRIP: 0010:skb_panic+0x5d/0x60  \nCode: c6 63 8b 8f bb 4c 0f 45 f6 48 c7 c7 4d 89 8b bb 48 89 ce 44 89 d1 41 56 53 41 53 ff b0 c8 00 00 00 e8 27 5f 23 00 48 83 c4 20  0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44  \nRSP: 0018:ffffaa700144bad0 EFLAGS: 00010282  \nRAX: 0000000000000089 RBX: 0000000000000140 RCX: 14432c5aad26c900  \nRDX: 0000000000000000 RSI: 00000000ffffdfff RDI: 0000000000000001  \nRBP: ffffaa700144bae0 R08: 0000000000000000 R09: ffffaa700144b920  \nR10: 00000000ffffdfff R11: ffffffffbc28fbc0 R12: ffff8fba4e57a010  \nR13: 0000000000000000 R14: ffffffffbb8f8b63 R15: 0000000000000000  \nFS:  0000000000000000(0000) GS:ffff8fba7bd00000(0000) knlGS:0000000000000000  \nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033  \nCR2: 00007999c4ad1000 CR3: 000000015503a000 CR4: 0000000000350ee0  \nCall Trace:  \n   \n ? __die_body+0x1f/0x70  \n ? die+0x3d/0x60  \n ? do_trap+0xa4/0x110  \n ? skb_panic+0x5d/0x60  \n ? do_error_trap+0x6d/0x90  \n ? skb_panic+0x5d/0x60  \n ? handle_invalid_op+0x30/0x40  \n ? skb_panic+0x5d/0x60  \n ? exc_invalid_op+0x3c/0x50  \n ? asm_exc_invalid_op+0x16/0x20  \n ? skb_panic+0x5d/0x60  \n skb_put+0x49/0x50  \n rtw89_fw_h2c_wow_gtk_ofld+0xbd/0x220 [rtw89_core 778b32de31cd1f14df2d6721ae99ba8a83636fa5]  \n rtw89_wow_resume+0x31f/0x540 [rtw89_core 778b32de31cd1f14df2d6721ae99ba8a83636fa5]  \n rtw89_ops_resume+0x2b/0xa0 [rtw89_core 778b32de31cd1f14df2d6721ae99ba8a83636fa5]  \n ieee80211_reconfig+0x84/0x13e0 [mac80211 818a894e3b77da6298269c59ed7cdff065a4ed52]  \n ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 1a793119e2aeb157c4ca4091ff8e1d9ae233b59d]  \n ? dev_printk_emit+0x51/0x70  \n ? _dev_info+0x6e/0x90  \n ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 1a793119e2aeb157c4ca4091ff8e1d9ae233b59d]  \n wiphy_resume+0x89/0x180 [cfg80211 1a793119e2aeb157c4ca4091ff8e1d9ae233b59d]  \n ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 1a793119e2aeb157c4ca4091ff8e1d9ae233b59d]  \n dpm_run_callback+0x3c/0x140  \n device_resume+0x1f9/0x3c0  \n ? __pfx_dpm_watchdog_handler+0x10/0x10  \n async_resume+0x1d/0x30  \n async_run_entry_fn+0x29/0xd0  \n process_scheduled_works+0x1d8/0x3d0  \n worker_thread+0x1fc/0x2f0  \n kthread+0xed/0x110  \n ? __pfx_worker_thread+0x10/0x10  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork+0x38/0x50  \n ? __pfx_kthread+0x10/0x10  \n ret_from_fork_asm+0x1b/0x30  \n   \nModules linked in: ccm 8021q r8153_ecm cdc_ether usbnet r8152 mii dm_integrity async_xor xor async_tx lz4 lz4_compress zstd zstd_compress zram zsmalloc uinput rfcomm cmac algif_hash rtw89_8922ae(O) algif_skcipher rtw89_8922a(O) af_alg rtw89_pci(O) rtw89_core(O) btusb(O) snd_soc_sst_bxt_da7219_max98357a btbcm(O) snd_soc_hdac_hdmi btintel(O) snd_soc_intel_hda_dsp_common snd_sof_probes btrtl(O) btmtk(O) snd_hda_codec_hdmi snd_soc_dmic uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_sof_pci_intel_apl snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda soundwire_intel soundwire_generic_allocation snd_sof_intel_hda_mlink soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp mac80211 snd_soc_acpi_intel_match snd_soc_acpi snd_sof snd_sof_utils soundwire_bus s[...]", "creation_timestamp": "2024-08-17T13:10:00.000000Z"}, {"uuid": "83264b9d-b9ec-4df7-b156-bf03ed8ef16f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43846", "type": "seen", "source": "https://t.me/cvedetector/3426", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43846 - Mellanox Technologies MSN3700/VMOD0005 Linux Kernel lib objagg Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43846 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nlib: objagg: Fix general protection fault  \n  \nThe library supports aggregation of objects into other objects only if  \nthe parent object does not have a parent itself. That is, nesting is not  \nsupported.  \n  \nAggregation happens in two cases: Without and with hints, where hints  \nare a pre-computed recommendation on how to aggregate the provided  \nobjects.  \n  \nNesting is not possible in the first case due to a check that prevents  \nit, but in the second case there is no check because the assumption is  \nthat nesting cannot happen when creating objects based on hints. The  \nviolation of this assumption leads to various warnings and eventually to  \na general protection fault [1].  \n  \nBefore fixing the root cause, error out when nesting happens and warn.  \n  \n[1]  \ngeneral protection fault, probably for non-canonical address 0xdead000000000d90: 0000 [#1] PREEMPT SMP PTI  \nCPU: 1 PID: 1083 Comm: kworker/1:9 Tainted: G        W          6.9.0-rc6-custom-gd9b4f1cca7fb #7  \nHardware name: Mellanox Technologies Ltd. MSN3700/VMOD0005, BIOS 5.11 01/06/2019  \nWorkqueue: mlxsw_core mlxsw_sp_acl_tcam_vregion_rehash_work  \nRIP: 0010:mlxsw_sp_acl_erp_bf_insert+0x25/0x80  \n[...]  \nCall Trace:  \n   \n mlxsw_sp_acl_atcam_entry_add+0x256/0x3c0  \n mlxsw_sp_acl_tcam_entry_create+0x5e/0xa0  \n mlxsw_sp_acl_tcam_vchunk_migrate_one+0x16b/0x270  \n mlxsw_sp_acl_tcam_vregion_rehash_work+0xbe/0x510  \n process_one_work+0x151/0x370  \n worker_thread+0x2cb/0x3e0  \n kthread+0xd0/0x100  \n ret_from_fork+0x34/0x50  \n ret_from_fork_asm+0x1a/0x30 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:21.000000Z"}, {"uuid": "d92780d4-0eb0-489f-9fb2-f96a719dbbb1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43841", "type": "seen", "source": "https://t.me/cvedetector/3423", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43841 - \"Wifi Virt_wifi SSID Spoofing Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-43841 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: virt_wifi: avoid reporting connection success with wrong SSID  \n  \nWhen user issues a connection with a different SSID than the one  \nvirt_wifi has advertised, the __cfg80211_connect_result() will  \ntrigger the warning: WARN_ON(bss_not_found).  \n  \nThe issue is because the connection code in virt_wifi does not  \ncheck the SSID from user space (it only checks the BSSID), and  \nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS  \neven if the SSID is different from the one virt_wifi has advertised.  \nEventually cfg80211 won't be able to find the cfg80211_bss and generate  \nthe warning.  \n  \nFixed it by checking the SSID (from user space) in the connection code. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:18.000000Z"}, {"uuid": "aac120b3-578e-4250-b7e6-6bb0f4de1e38", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-43848", "type": "seen", "source": "https://t.me/cvedetector/3422", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43848 - Qualcomm wifi Linux Kernel Denial of Service\", \n  \"Content\": \"CVE ID : CVE-2024-43848 \nPublished : Aug. 17, 2024, 10:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: mac80211: fix TTLM teardown work  \n  \nThe worker calculates the wrong sdata pointer, so if it ever  \nruns, it'll crash. Fix that. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"17 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-17T13:09:17.000000Z"}]}