<?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://db.gcve.eu</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, 22 May 2026 04:48:28 +0000</lastBuildDate>
    <item>
      <title>8217826c-87f1-4b50-8ffd-3d2b2e97a649</title>
      <link>https://db.gcve.eu/sighting/8217826c-87f1-4b50-8ffd-3d2b2e97a649/export</link>
      <description>{"uuid": "8217826c-87f1-4b50-8ffd-3d2b2e97a649", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44965", "type": "seen", "source": "https://t.me/cvedetector/4846", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44965 - \"Linux x86 PMD Alignment Assumption Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-44965 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nx86/mm: Fix pti_clone_pgtable() alignment assumption  \n  \nGuenter reported dodgy crashes on an i386-nosmp build using GCC-11  \nthat had the form of endless traps until entry stack exhaust and then  \n#DF from the stack guard.  \n  \nIt turned out that pti_clone_pgtable() had alignment assumptions on  \nthe start address, notably it hard assumes start is PMD aligned. This  \nis true on x86_64, but very much not true on i386.  \n  \nThese assumptions can cause the end condition to malfunction, leading  \nto a 'short' clone. Guess what happens when the user mapping has a  \nshort copy of the entry text?  \n  \nUse the correct increment form for addr to avoid alignment  \nassumptions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:56:26.000000Z"}</description>
      <content:encoded>{"uuid": "8217826c-87f1-4b50-8ffd-3d2b2e97a649", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44965", "type": "seen", "source": "https://t.me/cvedetector/4846", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44965 - \"Linux x86 PMD Alignment Assumption Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-44965 \nPublished : Sept. 4, 2024, 7:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nx86/mm: Fix pti_clone_pgtable() alignment assumption  \n  \nGuenter reported dodgy crashes on an i386-nosmp build using GCC-11  \nthat had the form of endless traps until entry stack exhaust and then  \n#DF from the stack guard.  \n  \nIt turned out that pti_clone_pgtable() had alignment assumptions on  \nthe start address, notably it hard assumes start is PMD aligned. This  \nis true on x86_64, but very much not true on i386.  \n  \nThese assumptions can cause the end condition to malfunction, leading  \nto a 'short' clone. Guess what happens when the user mapping has a  \nshort copy of the entry text?  \n  \nUse the correct increment form for addr to avoid alignment  \nassumptions. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T21:56:26.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/8217826c-87f1-4b50-8ffd-3d2b2e97a649/export</guid>
      <pubDate>Wed, 04 Sep 2024 21:56:26 +0000</pubDate>
    </item>
    <item>
      <title>26cf8daf-74fa-45a9-a89e-dcb880e93f61</title>
      <link>https://db.gcve.eu/sighting/26cf8daf-74fa-45a9-a89e-dcb880e93f61/export</link>
      <description>{"uuid": "26cf8daf-74fa-45a9-a89e-dcb880e93f61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44965", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}</description>
      <content:encoded>{"uuid": "26cf8daf-74fa-45a9-a89e-dcb880e93f61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44965", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-226-07", "content": "", "creation_timestamp": "2025-08-14T10:00:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/26cf8daf-74fa-45a9-a89e-dcb880e93f61/export</guid>
      <pubDate>Thu, 14 Aug 2025 10:00:00 +0000</pubDate>
    </item>
  </channel>
</rss>
