{"vulnerability": "CVE-2024-4767", "sightings": [{"uuid": "ab806600-e20f-4797-acbc-9dc2dc1c0309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47673", "type": "seen", "source": "https://t.me/cvedetector/7497", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47673 - Intel iwlwifi Firmware Stop State Access Control Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47673 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped  \n  \nNot doing so will make us send a host command to the transport while the  \nfirmware is not alive, which will trigger a WARNING.  \n  \nbad state = 0  \nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]  \nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]  \nCall Trace:  \n   \n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]  \n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]  \n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]  \n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]  \n process_one_work+0x29e/0x640  \n worker_thread+0x2df/0x690  \n ? rescuer_thread+0x540/0x540  \n kthread+0x192/0x1e0  \n ? set_kthread_struct+0x90/0x90  \n ret_from_fork+0x22/0x30 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:55.000000Z"}, {"uuid": "2d012a0d-824e-4f40-aa44-1a9735322ee6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47671", "type": "seen", "source": "https://t.me/cvedetector/7489", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47671 - Linux Kernel: USB usbtmc Information Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47671 \nPublished : Oct. 9, 2024, 3:15 p.m. | 39\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nUSB: usbtmc: prevent kernel-usb-infoleak  \n  \nThe syzbot reported a kernel-usb-infoleak in usbtmc_write,  \nwe need to clear the structure before filling fields. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-09T18:09:47.000000Z"}, {"uuid": "0ffa59ed-9311-41b4-a1f5-e312a5aed01a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47679", "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": "8d804658-54c6-430f-9d0e-bdf0a1c60bab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47678", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "008c90cb-c6f6-407d-a677-4e34f3859e3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2024-47678", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "207d9c9b-a476-457d-bfd1-bbce4dc9ee9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47674", "type": "seen", "source": "https://t.me/cvedetector/7904", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47674 - Linux Kernel PFN Mapping Key Immediate Object Destruction\", \n  \"Content\": \"CVE ID : CVE-2024-47674 \nPublished : Oct. 15, 2024, 11:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmm: avoid leaving partial pfn mappings around in error case  \n  \nAs Jann points out, PFN mappings are special, because unlike normal  \nmemory mappings, there is no lifetime information associated with the  \nmapping - it is just a raw mapping of PFNs with no reference counting of  \na 'struct page'.  \n  \nThat's all very much intentional, but it does mean that it's easy to  \nmess up the cleanup in case of errors.  Yes, a failed mmap() will always  \neventually clean up any partial mappings, but without any explicit  \nlifetime in the page table mapping itself, it's very easy to do the  \nerror handling in the wrong order.  \n  \nIn particular, it's easy to mistakenly free the physical backing store  \nbefore the page tables are actually cleaned up and (temporarily) have  \nstale dangling PTE entries.  \n  \nTo make this situation less error-prone, just make sure that any partial  \npfn mapping is torn down early, before any other error handling. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-15T14:25:43.000000Z"}, {"uuid": "740c34e0-2cb2-49b1-aacb-d27cb4e32b4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-47673", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}]}