<?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>Wed, 23 Sep 2026 08:01:19 +0000</lastBuildDate>
    <item>
      <title>0437d198-0226-498b-b0ff-22344bd81ee4</title>
      <link>https://vulnerability.circl.lu/sighting/0437d198-0226-498b-b0ff-22344bd81ee4/export</link>
      <description>{"uuid": "0437d198-0226-498b-b0ff-22344bd81ee4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53129", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14517", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53129\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\next4: Fix deadlock during directory rename\n\nAs lockdep properly warns, we should not be locking i_rwsem while having\ntransactions started as the proper lock ordering used by all directory\nhandling operations is i_rwsem -&amp;gt; transaction start. Fix the lock\nordering by moving the locking of the directory earlier in\next4_rename().\n\ud83d\udccf Published: 2025-05-02T15:56:04.366Z\n\ud83d\udccf Modified: 2025-05-02T15:56:04.366Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6b06c4ae64e3557a19b3bb0b6dbf641bc41fc218\n2. https://git.kernel.org/stable/c/b113f90204479f55a17295bedf0cc966a60c7a56\n3. https://git.kernel.org/stable/c/a2bc806e95bde8de3a0d675051d9ae78dcf6c691\n4. https://git.kernel.org/stable/c/2ef7f829214fa8f428d953b49557b89b2b02db66\n5. https://git.kernel.org/stable/c/352c728653a1179ce7bb37a4c8aa8404d83914a2\n6. https://git.kernel.org/stable/c/3c92792da8506a295afb6d032b4476e46f979725", "creation_timestamp": "2025-05-02T16:16:14.000000Z"}</description>
      <content:encoded>{"uuid": "0437d198-0226-498b-b0ff-22344bd81ee4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53129", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14517", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53129\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\next4: Fix deadlock during directory rename\n\nAs lockdep properly warns, we should not be locking i_rwsem while having\ntransactions started as the proper lock ordering used by all directory\nhandling operations is i_rwsem -&amp;gt; transaction start. Fix the lock\nordering by moving the locking of the directory earlier in\next4_rename().\n\ud83d\udccf Published: 2025-05-02T15:56:04.366Z\n\ud83d\udccf Modified: 2025-05-02T15:56:04.366Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6b06c4ae64e3557a19b3bb0b6dbf641bc41fc218\n2. https://git.kernel.org/stable/c/b113f90204479f55a17295bedf0cc966a60c7a56\n3. https://git.kernel.org/stable/c/a2bc806e95bde8de3a0d675051d9ae78dcf6c691\n4. https://git.kernel.org/stable/c/2ef7f829214fa8f428d953b49557b89b2b02db66\n5. https://git.kernel.org/stable/c/352c728653a1179ce7bb37a4c8aa8404d83914a2\n6. https://git.kernel.org/stable/c/3c92792da8506a295afb6d032b4476e46f979725", "creation_timestamp": "2025-05-02T16:16:14.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/0437d198-0226-498b-b0ff-22344bd81ee4/export</guid>
      <pubDate>Fri, 02 May 2025 16:16:14 +0000</pubDate>
    </item>
  </channel>
</rss>
