<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T16:43:56.259316+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2023-52732</id>
    <title>CVE-2023-52732 — ceph: blocklist the kclient when receiving corrupted snap trace</title>
    <updated>2026-09-29T16:43:56.275084+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>ceph: blocklist the kclient when receiving corrupted snap trace</p>
<p>When received corrupted snap trace we don't know what exactly has
happened in MDS side. And we shouldn't continue IOs and metadatas
access to MDS, which may corrupt or get incorrect contents.</p>
<p>This patch will just block all the further IO/MDS requests
immediately and then evict the kclient itself.</p>
<p>The reason why we still need to evict the kclient just after
blocking all the further IOs is that the MDS could revoke the caps
faster.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-52732"/>
  </entry>
</feed>
