<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T22:49:32.173376+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2024-35998</id>
    <title>CVE-2024-35998 — smb3: fix lock ordering potential deadlock in cifs_sync_mid_result</title>
    <updated>2026-10-05T22:49:32.190119+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>smb3: fix lock ordering potential deadlock in cifs_sync_mid_result</p>
<p>Coverity spotted that the cifs_sync_mid_result function could deadlock</p>
<p>"Thread deadlock (ORDER_REVERSAL) lock_order: Calling spin_lock acquires
lock TCP_Server_Info.srv_lock while holding lock TCP_Server_Info.mid_lock"</p>
<p>Addresses-Coverity: 1590401 ("Thread deadlock (ORDER_REVERSAL)")</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-35998"/>
  </entry>
</feed>
