<?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>Thu, 28 May 2026 17:33:14 +0000</lastBuildDate>
    <item>
      <title>0a46e5ad-8baa-4a30-9c1b-0085f9f594ad</title>
      <link>https://vulnerability.circl.lu/sighting/0a46e5ad-8baa-4a30-9c1b-0085f9f594ad/export</link>
      <description>{"uuid": "0a46e5ad-8baa-4a30-9c1b-0085f9f594ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzohx3e2e", "content": "", "creation_timestamp": "2024-12-27T15:20:16.415258Z"}</description>
      <content:encoded>{"uuid": "0a46e5ad-8baa-4a30-9c1b-0085f9f594ad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lecbzohx3e2e", "content": "", "creation_timestamp": "2024-12-27T15:20:16.415258Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/0a46e5ad-8baa-4a30-9c1b-0085f9f594ad/export</guid>
      <pubDate>Fri, 27 Dec 2024 15:20:16 +0000</pubDate>
    </item>
    <item>
      <title>77aac787-7f49-4d3c-8057-820c82cde33f</title>
      <link>https://vulnerability.circl.lu/sighting/77aac787-7f49-4d3c-8057-820c82cde33f/export</link>
      <description>{"uuid": "77aac787-7f49-4d3c-8057-820c82cde33f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://t.me/cvedetector/13778", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56654 - Linux Bluetooth RCU List Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56654 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: hci_event: Fix using rcu_read_(un)lock while iterating  \n  \nThe usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is  \nnot safe since for the most part entries fetched this way shall be  \ntreated as rcu_dereference:  \n  \n Note that the value returned by rcu_dereference() is valid  \n only within the enclosing RCU read-side critical section [1]_.  \n For example, the following is **not** legal::  \n  \n  rcu_read_lock();  \n  p = rcu_dereference(head.next);  \n  rcu_read_unlock();  \n  x = p-&amp;gt;address; /* BUG!!! */  \n  rcu_read_lock();  \n  y = p-&amp;gt;data; /* BUG!!! */  \n  rcu_read_unlock(); \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:12.000000Z"}</description>
      <content:encoded>{"uuid": "77aac787-7f49-4d3c-8057-820c82cde33f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56654", "type": "seen", "source": "https://t.me/cvedetector/13778", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56654 - Linux Bluetooth RCU List Corruption Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56654 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nBluetooth: hci_event: Fix using rcu_read_(un)lock while iterating  \n  \nThe usage of rcu_read_(un)lock while inside list_for_each_entry_rcu is  \nnot safe since for the most part entries fetched this way shall be  \ntreated as rcu_dereference:  \n  \n Note that the value returned by rcu_dereference() is valid  \n only within the enclosing RCU read-side critical section [1]_.  \n For example, the following is **not** legal::  \n  \n  rcu_read_lock();  \n  p = rcu_dereference(head.next);  \n  rcu_read_unlock();  \n  x = p-&amp;gt;address; /* BUG!!! */  \n  rcu_read_lock();  \n  y = p-&amp;gt;data; /* BUG!!! */  \n  rcu_read_unlock(); \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:51:12.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/77aac787-7f49-4d3c-8057-820c82cde33f/export</guid>
      <pubDate>Fri, 27 Dec 2024 16:51:12 +0000</pubDate>
    </item>
  </channel>
</rss>
