<?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>Thu, 21 May 2026 06:09:16 +0000</lastBuildDate>
    <item>
      <title>5b9f9b7a-cab1-49df-b228-78907d4bb290</title>
      <link>https://db.gcve.eu/sighting/5b9f9b7a-cab1-49df-b228-78907d4bb290/export</link>
      <description>{"uuid": "5b9f9b7a-cab1-49df-b228-78907d4bb290", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-47351", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14720", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-47351\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: Fix races between xattr_{set|get} and listxattr operations\n\nUBIFS may occur some problems with concurrent xattr_{set|get} and\nlistxattr operations, such as assertion failure, memory corruption,\nstale xattr value[1].\n\nFix it by importing a new rw-lock in @ubifs_inode to serilize write\noperations on xattr, concurrent read operations are still effective,\njust like ext4.\n\n[1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com\n\ud83d\udccf Published: 2024-05-21T14:35:55.806Z\n\ud83d\udccf Modified: 2025-05-04T07:09:10.505Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7adc05b73d91a5e3d4ca7714fa53ad9b70c53d08\n2. https://git.kernel.org/stable/c/38dde03eb239605f428f3f1e4baa73d4933a4cc6\n3. https://git.kernel.org/stable/c/9558612cb829f2c022b788f55d6b8437d5234a82\n4. https://git.kernel.org/stable/c/c0756f75c22149d20fcb7d8409827cee905eb386\n5. https://git.kernel.org/stable/c/f4e3634a3b642225a530c292fdb1e8a4007507f5", "creation_timestamp": "2025-05-04T07:17:54.000000Z"}</description>
      <content:encoded>{"uuid": "5b9f9b7a-cab1-49df-b228-78907d4bb290", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-47351", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14720", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-47351\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: Fix races between xattr_{set|get} and listxattr operations\n\nUBIFS may occur some problems with concurrent xattr_{set|get} and\nlistxattr operations, such as assertion failure, memory corruption,\nstale xattr value[1].\n\nFix it by importing a new rw-lock in @ubifs_inode to serilize write\noperations on xattr, concurrent read operations are still effective,\njust like ext4.\n\n[1] https://lore.kernel.org/linux-mtd/20200630130438.141649-1-houtao1@huawei.com\n\ud83d\udccf Published: 2024-05-21T14:35:55.806Z\n\ud83d\udccf Modified: 2025-05-04T07:09:10.505Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/7adc05b73d91a5e3d4ca7714fa53ad9b70c53d08\n2. https://git.kernel.org/stable/c/38dde03eb239605f428f3f1e4baa73d4933a4cc6\n3. https://git.kernel.org/stable/c/9558612cb829f2c022b788f55d6b8437d5234a82\n4. https://git.kernel.org/stable/c/c0756f75c22149d20fcb7d8409827cee905eb386\n5. https://git.kernel.org/stable/c/f4e3634a3b642225a530c292fdb1e8a4007507f5", "creation_timestamp": "2025-05-04T07:17:54.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/5b9f9b7a-cab1-49df-b228-78907d4bb290/export</guid>
      <pubDate>Sun, 04 May 2025 07:17:54 +0000</pubDate>
    </item>
  </channel>
</rss>
