<?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://cve.radiocsirt.org</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>Sat, 03 Oct 2026 10:24:18 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06040</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06040</link>
      <description>bdu:2025-06040</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06040</guid>
    </item>
    <item>
      <title>EUVD-2026-320280</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320280</link>
      <description>EUVD-2026-320280</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320280</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49068</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49068</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: release correct delalloc amount in direct IO write path&lt;/p&gt;
&lt;p&gt;Running generic/406 causes the following WARNING in btrfs_destroy_inode()
which tells there are outstanding extents left.&lt;/p&gt;
&lt;p&gt;In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding
extents with btrfs_delalloc_reserve_metadata() (or indirectly from
btrfs_delalloc_reserve_space(()). We then release the outstanding extents
with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified
in the COW case, which releases fewer outstanding extents than expected.&lt;/p&gt;
&lt;p&gt;Fix it by calling btrfs_delalloc_release_extents() for the original length.&lt;/p&gt;
&lt;p&gt;To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s
triggering a short-write, due to not being able to allocate a large
extent and instead allocating a smaller one.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  Modules linked in: btrfs blake2b_generic xor lzo_compress
  lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram
  zsmalloc
  CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014
  RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206
  RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000
  RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78
  RBP: ffff888100…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: release correct delalloc amount in direct IO write path&lt;/p&gt;
&lt;p&gt;Running generic/406 causes the following WARNING in btrfs_destroy_inode()
which tells there are outstanding extents left.&lt;/p&gt;
&lt;p&gt;In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding
extents with btrfs_delalloc_reserve_metadata() (or indirectly from
btrfs_delalloc_reserve_space(()). We then release the outstanding extents
with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified
in the COW case, which releases fewer outstanding extents than expected.&lt;/p&gt;
&lt;p&gt;Fix it by calling btrfs_delalloc_release_extents() for the original length.&lt;/p&gt;
&lt;p&gt;To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s
triggering a short-write, due to not being able to allocate a large
extent and instead allocating a smaller one.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  Modules linked in: btrfs blake2b_generic xor lzo_compress
  lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram
  zsmalloc
  CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014
  RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206
  RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000
  RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78
  RBP: ffff888100…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49068</guid>
    </item>
    <item>
      <title>GHSA-vm76-7cfx-c7v2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vm76-7cfx-c7v2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: release correct delalloc amount in direct IO write path&lt;/p&gt;
&lt;p&gt;Running generic/406 causes the following WARNING in btrfs_destroy_inode()
which tells there are outstanding extents left.&lt;/p&gt;
&lt;p&gt;In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding
extents with btrfs_delalloc_reserve_metadata() (or indirectly from
btrfs_delalloc_reserve_space(()). We then release the outstanding extents
with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified
in the COW case, which releases fewer outstanding extents than expected.&lt;/p&gt;
&lt;p&gt;Fix it by calling btrfs_delalloc_release_extents() for the original length.&lt;/p&gt;
&lt;p&gt;To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s
triggering a short-write, due to not being able to allocate a large
extent and instead allocating a smaller one.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  Modules linked in: btrfs blake2b_generic xor lzo_compress
  lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram
  zsmalloc
  CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014
  RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206
  RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000
  RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78
  RBP: ffff888100…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: release correct delalloc amount in direct IO write path&lt;/p&gt;
&lt;p&gt;Running generic/406 causes the following WARNING in btrfs_destroy_inode()
which tells there are outstanding extents left.&lt;/p&gt;
&lt;p&gt;In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding
extents with btrfs_delalloc_reserve_metadata() (or indirectly from
btrfs_delalloc_reserve_space(()). We then release the outstanding extents
with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified
in the COW case, which releases fewer outstanding extents than expected.&lt;/p&gt;
&lt;p&gt;Fix it by calling btrfs_delalloc_release_extents() for the original length.&lt;/p&gt;
&lt;p&gt;To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s
triggering a short-write, due to not being able to allocate a large
extent and instead allocating a smaller one.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  Modules linked in: btrfs blake2b_generic xor lzo_compress
  lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram
  zsmalloc
  CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014
  RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]
  RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206
  RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000
  RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78
  RBP: ffff888100…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vm76-7cfx-c7v2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49068</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49068</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 84 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: release correct delalloc amount in direct IO write path Running generic/406 causes the following WARNING in btrfs_destroy_inode() which tells there are outstanding extents left. In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding extents with btrfs_delalloc_reserve_metadata() (or indirectly from btrfs_delalloc_reserve_space(()). We then release the outstanding extents with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified in the COW case, which releases fewer outstanding extents than expected. Fix it by calling btrfs_delalloc_release_extents() for the original length. To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s triggering a short-write, due to not being able to allocate a large extent and instead allocating a smaller one.   WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]   Modules linked in: btrfs blake2b_generic xor lzo_compress   lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram   zsmalloc   CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014   RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]   RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206   RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000   RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78   RBP: ffff888100548940…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 84 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: release correct delalloc amount in direct IO write path Running generic/406 causes the following WARNING in btrfs_destroy_inode() which tells there are outstanding extents left. In btrfs_get_blocks_direct_write(), we reserve a temporary outstanding extents with btrfs_delalloc_reserve_metadata() (or indirectly from btrfs_delalloc_reserve_space(()). We then release the outstanding extents with btrfs_delalloc_release_extents(). However, the &amp;#34;len&amp;#34; can be modified in the COW case, which releases fewer outstanding extents than expected. Fix it by calling btrfs_delalloc_release_extents() for the original length. To reproduce the warning, the filesystem should be 1 GiB.  It&amp;#39;s triggering a short-write, due to not being able to allocate a large extent and instead allocating a smaller one.   WARNING: CPU: 0 PID: 757 at fs/btrfs/inode.c:8848 btrfs_destroy_inode+0x1e6/0x210 [btrfs]   Modules linked in: btrfs blake2b_generic xor lzo_compress   lzo_decompress raid6_pq zstd zstd_decompress zstd_compress xxhash zram   zsmalloc   CPU: 0 PID: 757 Comm: umount Not tainted 5.17.0-rc8+ #101   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS d55cb5a 04/01/2014   RIP: 0010:btrfs_destroy_inode+0x1e6/0x210 [btrfs]   RSP: 0018:ffffc9000327bda8 EFLAGS: 00010206   RAX: 0000000000000000 RBX: ffff888100548b78 RCX: 0000000000000000   RDX: 0000000000026900 RSI: 0000000000000000 RDI: ffff888100548b78   RBP: ffff888100548940…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49068</guid>
    </item>
  </channel>
</rss>
