<?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 16:20:44 +0000</lastBuildDate>
    <item>
      <title>52b33ae2-9a00-4cc6-a446-4994a431bdef</title>
      <link>https://vulnerability.circl.lu/sighting/52b33ae2-9a00-4cc6-a446-4994a431bdef/export</link>
      <description>{"uuid": "52b33ae2-9a00-4cc6-a446-4994a431bdef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39477", "type": "seen", "source": "https://t.me/cvedetector/87", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39477 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-39477 \nPublished : July 5, 2024, 7:15 a.m. | 17\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmm/hugetlb: do not call vma_add_reservation upon ENOMEM \n \nsysbot reported a splat [1] on __unmap_hugepage_range().  This is because \nvma_needs_reservation() can return -ENOMEM if \nallocate_file_region_entries() fails to allocate the file_region struct \nfor the reservation. \n \nCheck for that and do not call vma_add_reservation() if that is the case, \notherwise region_abort() and region_del() will see that we do not have any \nfile_regions. \n \nIf we detect that vma_needs_reservation() returned -ENOMEM, we clear the \nhugetlb_restore_reserve flag as if this reservation was still consumed, so \nfree_huge_folio() will not increment the resv count. \n \n[1]  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-05T09:34:12.000000Z"}</description>
      <content:encoded>{"uuid": "52b33ae2-9a00-4cc6-a446-4994a431bdef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39477", "type": "seen", "source": "https://t.me/cvedetector/87", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39477 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-39477 \nPublished : July 5, 2024, 7:15 a.m. | 17\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nmm/hugetlb: do not call vma_add_reservation upon ENOMEM \n \nsysbot reported a splat [1] on __unmap_hugepage_range().  This is because \nvma_needs_reservation() can return -ENOMEM if \nallocate_file_region_entries() fails to allocate the file_region struct \nfor the reservation. \n \nCheck for that and do not call vma_add_reservation() if that is the case, \notherwise region_abort() and region_del() will see that we do not have any \nfile_regions. \n \nIf we detect that vma_needs_reservation() returned -ENOMEM, we clear the \nhugetlb_restore_reserve flag as if this reservation was still consumed, so \nfree_huge_folio() will not increment the resv count. \n \n[1]  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-05T09:34:12.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/52b33ae2-9a00-4cc6-a446-4994a431bdef/export</guid>
      <pubDate>Fri, 05 Jul 2024 09:34:12 +0000</pubDate>
    </item>
  </channel>
</rss>
