<?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>Tue, 05 May 2026 19:56:50 +0000</lastBuildDate>
    <item>
      <title>d92780d4-0eb0-489f-9fb2-f96a719dbbb1</title>
      <link>https://vulnerability.circl.lu/sighting/d92780d4-0eb0-489f-9fb2-f96a719dbbb1/export</link>
      <description>{"uuid": "d92780d4-0eb0-489f-9fb2-f96a719dbbb1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"}</description>
      <content:encoded>{"uuid": "d92780d4-0eb0-489f-9fb2-f96a719dbbb1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "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"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/d92780d4-0eb0-489f-9fb2-f96a719dbbb1/export</guid>
      <pubDate>Sat, 17 Aug 2024 13:09:18 +0000</pubDate>
    </item>
  </channel>
</rss>
