<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 09 May 2026 23:28:34 +0000</lastBuildDate>
    <item>
      <title>ab806600-e20f-4797-acbc-9dc2dc1c0309</title>
      <link>https://vulnerability.circl.lu/sighting/ab806600-e20f-4797-acbc-9dc2dc1c0309/export</link>
      <description>{"uuid": "ab806600-e20f-4797-acbc-9dc2dc1c0309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"}</description>
      <content:encoded>{"uuid": "ab806600-e20f-4797-acbc-9dc2dc1c0309", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/ab806600-e20f-4797-acbc-9dc2dc1c0309/export</guid>
      <pubDate>Wed, 09 Oct 2024 18:09:55 +0000</pubDate>
    </item>
    <item>
      <title>740c34e0-2cb2-49b1-aacb-d27cb4e32b4f</title>
      <link>https://vulnerability.circl.lu/sighting/740c34e0-2cb2-49b1-aacb-d27cb4e32b4f/export</link>
      <description>{"uuid": "740c34e0-2cb2-49b1-aacb-d27cb4e32b4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "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"}</description>
      <content:encoded>{"uuid": "740c34e0-2cb2-49b1-aacb-d27cb4e32b4f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "c933734a-9be8-4142-889e-26e95c752803", "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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/740c34e0-2cb2-49b1-aacb-d27cb4e32b4f/export</guid>
      <pubDate>Wed, 03 Dec 2025 14:14:49 +0000</pubDate>
    </item>
  </channel>
</rss>
