<?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>Sat, 09 May 2026 17:22:36 +0000</lastBuildDate>
    <item>
      <title>187801ea-2c7e-44ac-995b-53ead82e1014</title>
      <link>https://vulnerability.circl.lu/sighting/187801ea-2c7e-44ac-995b-53ead82e1014/export</link>
      <description>{"uuid": "187801ea-2c7e-44ac-995b-53ead82e1014", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21900", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/9921", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21900\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4: Fix a deadlock when recovering state on a sillyrenamed file\n\nIf the file is sillyrenamed, and slated for delete on close, it is\npossible for a server reboot to triggeer an open reclaim, with can again\nrace with the application call to close(). When that happens, the call\nto put_nfs_open_context() can trigger a synchronous delegreturn call\nwhich deadlocks because it is not marked as privileged.\n\nInstead, ensure that the call to nfs4_inode_return_delegation_on_close()\ncatches the delegreturn, and schedules it asynchronously.\n\ud83d\udccf Published: 2025-04-01T15:26:51.290Z\n\ud83d\udccf Modified: 2025-04-01T15:26:51.290Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4fe4ae6c2e01d028856b73b6328b12b8945df871\n2. https://git.kernel.org/stable/c/f41a60bc43e7abbc636fee78bed0d74c31e738b0\n3. https://git.kernel.org/stable/c/8f8df955f078e1a023ee55161935000a67651f38", "creation_timestamp": "2025-04-01T15:32:38.000000Z"}</description>
      <content:encoded>{"uuid": "187801ea-2c7e-44ac-995b-53ead82e1014", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21900", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/9921", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21900\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4: Fix a deadlock when recovering state on a sillyrenamed file\n\nIf the file is sillyrenamed, and slated for delete on close, it is\npossible for a server reboot to triggeer an open reclaim, with can again\nrace with the application call to close(). When that happens, the call\nto put_nfs_open_context() can trigger a synchronous delegreturn call\nwhich deadlocks because it is not marked as privileged.\n\nInstead, ensure that the call to nfs4_inode_return_delegation_on_close()\ncatches the delegreturn, and schedules it asynchronously.\n\ud83d\udccf Published: 2025-04-01T15:26:51.290Z\n\ud83d\udccf Modified: 2025-04-01T15:26:51.290Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4fe4ae6c2e01d028856b73b6328b12b8945df871\n2. https://git.kernel.org/stable/c/f41a60bc43e7abbc636fee78bed0d74c31e738b0\n3. https://git.kernel.org/stable/c/8f8df955f078e1a023ee55161935000a67651f38", "creation_timestamp": "2025-04-01T15:32:38.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/187801ea-2c7e-44ac-995b-53ead82e1014/export</guid>
      <pubDate>Tue, 01 Apr 2025 15:32:38 +0000</pubDate>
    </item>
  </channel>
</rss>
