<?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 entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 06:55:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26658 — bcachefs: grab s_umount only if snapshotting</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26658</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bcachefs: grab s_umount only if snapshotting&lt;/p&gt;
&lt;p&gt;When I was testing mongodb over bcachefs with compression,
there is a lockdep warning when snapshotting mongodb data volume.&lt;/p&gt;
&lt;p&gt;$ cat test.sh
prog=bcachefs&lt;/p&gt;
&lt;p&gt;$prog subvolume create /mnt/data
$prog subvolume create /mnt/data/snapshots&lt;/p&gt;
&lt;p&gt;while true;do
    $prog subvolume snapshot /mnt/data /mnt/data/snapshots/$(date +%s)
    sleep 1s
done&lt;/p&gt;
&lt;p&gt;$ cat /etc/mongodb.conf
systemLog:
  destination: file
  logAppend: true
  path: /mnt/data/mongod.log&lt;/p&gt;
&lt;p&gt;storage:
  dbPath: /mnt/data/&lt;/p&gt;
&lt;p&gt;lockdep reports:
[ 3437.452330] ======================================================
[ 3437.452750] WARNING: possible circular locking dependency detected
[ 3437.453168] 6.7.0-rc7-custom+ #85 Tainted: G            E
[ 3437.453562] ------------------------------------------------------
[ 3437.453981] bcachefs/35533 is trying to acquire lock:
[ 3437.454325] ffffa0a02b2b1418 (sb_writers#10){.+.+}-{0:0}, at: filename_create+0x62/0x190
[ 3437.454875]
               but task is already holding lock:
[ 3437.455268] ffffa0a02b2b10e0 (&amp;amp;type-&amp;gt;s_umount_key#48){.+.+}-{3:3}, at: bch2_fs_file_ioctl+0x232/0xc90 [bcachefs]
[ 3437.456009]
               which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;[ 3437.456553]
               the existing dependency chain (in reverse order) is:
[ 3437.457054]
               -&amp;gt; #3 (&amp;amp;type-&amp;gt;s_umount_key#48){.+.+}-{3:3}:
[ 3437.457507]        down_read+0x3e/0x170
[ 3437.457772]…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bcachefs: grab s_umount only if snapshotting&lt;/p&gt;
&lt;p&gt;When I was testing mongodb over bcachefs with compression,
there is a lockdep warning when snapshotting mongodb data volume.&lt;/p&gt;
&lt;p&gt;$ cat test.sh
prog=bcachefs&lt;/p&gt;
&lt;p&gt;$prog subvolume create /mnt/data
$prog subvolume create /mnt/data/snapshots&lt;/p&gt;
&lt;p&gt;while true;do
    $prog subvolume snapshot /mnt/data /mnt/data/snapshots/$(date +%s)
    sleep 1s
done&lt;/p&gt;
&lt;p&gt;$ cat /etc/mongodb.conf
systemLog:
  destination: file
  logAppend: true
  path: /mnt/data/mongod.log&lt;/p&gt;
&lt;p&gt;storage:
  dbPath: /mnt/data/&lt;/p&gt;
&lt;p&gt;lockdep reports:
[ 3437.452330] ======================================================
[ 3437.452750] WARNING: possible circular locking dependency detected
[ 3437.453168] 6.7.0-rc7-custom+ #85 Tainted: G            E
[ 3437.453562] ------------------------------------------------------
[ 3437.453981] bcachefs/35533 is trying to acquire lock:
[ 3437.454325] ffffa0a02b2b1418 (sb_writers#10){.+.+}-{0:0}, at: filename_create+0x62/0x190
[ 3437.454875]
               but task is already holding lock:
[ 3437.455268] ffffa0a02b2b10e0 (&amp;amp;type-&amp;gt;s_umount_key#48){.+.+}-{3:3}, at: bch2_fs_file_ioctl+0x232/0xc90 [bcachefs]
[ 3437.456009]
               which lock already depends on the new lock.&lt;/p&gt;
&lt;p&gt;[ 3437.456553]
               the existing dependency chain (in reverse order) is:
[ 3437.457054]
               -&amp;gt; #3 (&amp;amp;type-&amp;gt;s_umount_key#48){.+.+}-{3:3}:
[ 3437.457507]        down_read+0x3e/0x170
[ 3437.457772]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26658</guid>
    </item>
  </channel>
</rss>
