<?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>Fri, 08 May 2026 13:06:24 +0000</lastBuildDate>
    <item>
      <title>8242ce49-ce47-4f28-8937-c25d6b717310</title>
      <link>https://vulnerability.circl.lu/sighting/8242ce49-ce47-4f28-8937-c25d6b717310/export</link>
      <description>{"uuid": "8242ce49-ce47-4f28-8937-c25d6b717310", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50087", "type": "seen", "source": "https://t.me/cvedetector/9219", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50087 - Btrfs Uninitialized Pointer Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50087 \nPublished : Oct. 29, 2024, 1:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: fix uninitialized pointer free on read_alloc_one_name() error  \n  \nThe function read_alloc_one_name() does not initialize the name field of  \nthe passed fscrypt_str struct if kmalloc fails to allocate the  \ncorresponding buffer.  Thus, it is not guaranteed that  \nfscrypt_str.name is initialized when freeing it.  \n  \nThis is a follow-up to the linked patch that fixes the remaining  \ninstances of the bug introduced by commit e43eec81c516 (\"btrfs: use  \nstruct qstr instead of name and namelen pairs\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T03:02:53.000000Z"}</description>
      <content:encoded>{"uuid": "8242ce49-ce47-4f28-8937-c25d6b717310", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50087", "type": "seen", "source": "https://t.me/cvedetector/9219", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50087 - Btrfs Uninitialized Pointer Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50087 \nPublished : Oct. 29, 2024, 1:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbtrfs: fix uninitialized pointer free on read_alloc_one_name() error  \n  \nThe function read_alloc_one_name() does not initialize the name field of  \nthe passed fscrypt_str struct if kmalloc fails to allocate the  \ncorresponding buffer.  Thus, it is not guaranteed that  \nfscrypt_str.name is initialized when freeing it.  \n  \nThis is a follow-up to the linked patch that fixes the remaining  \ninstances of the bug introduced by commit e43eec81c516 (\"btrfs: use  \nstruct qstr instead of name and namelen pairs\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-29T03:02:53.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/8242ce49-ce47-4f28-8937-c25d6b717310/export</guid>
      <pubDate>Tue, 29 Oct 2024 03:02:53 +0000</pubDate>
    </item>
  </channel>
</rss>
