<?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>Wed, 30 Sep 2026 06:43:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56581 — btrfs: ref-verify: fix use-after-free after invalid ref action</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56581</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;btrfs: ref-verify: fix use-after-free after invalid ref action&lt;/p&gt;
&lt;p&gt;At btrfs_ref_tree_mod() after we successfully inserted the new ref entry
(local variable &amp;#39;ref&amp;#39;) into the respective block entry&amp;#39;s rbtree (local
variable &amp;#39;be&amp;#39;), if we find an unexpected action of BTRFS_DROP_DELAYED_REF,
we error out and free the ref entry without removing it from the block
entry&amp;#39;s rbtree. Then in the error path of btrfs_ref_tree_mod() we call
btrfs_free_ref_cache(), which iterates over all block entries and then
calls free_block_entry() for each one, and there we will trigger a
use-after-free when we are called against the block entry to which we
added the freed ref entry to its rbtree, since the rbtree still points
to the block entry, as we didn&amp;#39;t remove it from the rbtree before freeing
it in the error path at btrfs_ref_tree_mod(). Fix this by removing the
new ref entry from the rbtree before freeing it.&lt;/p&gt;
&lt;p&gt;Syzbot report this with the following stack traces:&lt;/p&gt;
&lt;p&gt;BTRFS error (device loop0 state EA):   Ref action 2, root 5, ref_root 0, parent 8564736, owner 0, offset 0, num_refs 18446744073709551615
      __btrfs_mod_ref+0x7dd/0xac0 fs/btrfs/extent-tree.c:2523
      update_ref_for_cow+0x9cd/0x11f0 fs/btrfs/ctree.c:512
      btrfs_force_cow_block+0x9f6/0x1da0 fs/btrfs/ctree.c:594
      btrfs_cow_block+0x35e/0xa40 fs/btrfs/ctree.c:754
      btrfs_search_slot+0xbdd/0x30d0 fs/btrfs/ctree.c:2116
      btrfs_insert_empty_items+0x9c/0x1a…&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;btrfs: ref-verify: fix use-after-free after invalid ref action&lt;/p&gt;
&lt;p&gt;At btrfs_ref_tree_mod() after we successfully inserted the new ref entry
(local variable &amp;#39;ref&amp;#39;) into the respective block entry&amp;#39;s rbtree (local
variable &amp;#39;be&amp;#39;), if we find an unexpected action of BTRFS_DROP_DELAYED_REF,
we error out and free the ref entry without removing it from the block
entry&amp;#39;s rbtree. Then in the error path of btrfs_ref_tree_mod() we call
btrfs_free_ref_cache(), which iterates over all block entries and then
calls free_block_entry() for each one, and there we will trigger a
use-after-free when we are called against the block entry to which we
added the freed ref entry to its rbtree, since the rbtree still points
to the block entry, as we didn&amp;#39;t remove it from the rbtree before freeing
it in the error path at btrfs_ref_tree_mod(). Fix this by removing the
new ref entry from the rbtree before freeing it.&lt;/p&gt;
&lt;p&gt;Syzbot report this with the following stack traces:&lt;/p&gt;
&lt;p&gt;BTRFS error (device loop0 state EA):   Ref action 2, root 5, ref_root 0, parent 8564736, owner 0, offset 0, num_refs 18446744073709551615
      __btrfs_mod_ref+0x7dd/0xac0 fs/btrfs/extent-tree.c:2523
      update_ref_for_cow+0x9cd/0x11f0 fs/btrfs/ctree.c:512
      btrfs_force_cow_block+0x9f6/0x1da0 fs/btrfs/ctree.c:594
      btrfs_cow_block+0x35e/0xa40 fs/btrfs/ctree.c:754
      btrfs_search_slot+0xbdd/0x30d0 fs/btrfs/ctree.c:2116
      btrfs_insert_empty_items+0x9c/0x1a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56581</guid>
    </item>
    <item>
      <title>LSN-0119-1 — Kernel Live Patch Security Notice</title>
      <link>https://vulnerability.circl.lu/vuln/lsn-0119-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle, Ubuntu:Pro:20.04:LTS: linux-aws-5.15 and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: btrfs: ref-verify: fix use-after-free after invalid ref action At
btrfs_ref_tree_mod() after we successfully inserted the new ref entry
(local variable &amp;#39;ref&amp;#39;) into the respective block entry&amp;#39;s rbtree (local
variable &amp;#39;be&amp;#39;), if we find an unexpected action of BTRFS_DROP_DELAYED_REF,
we error out and free the ref entry without removing it from the block
entry&amp;#39;s rbtree.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: net/smc: fix LGR and link use-after-free issue We encountered a
LGR/link use-after-free issue, which manifested as the LGR/link refcnt
reaching 0 early and entering the clear process, making resource access
unsafe.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: usb: cdc-acm: Check control transfer buffer size before access If
the first fragment is shorter than struct usb_cdc_notification, we can&amp;#39;t
calculate an expected_size.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: drm/amdgpu: avoid buffer overflow attach in
smu_sys_set_pp_table() It malicious user provides a small pptable through
sysfs and then a big…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle, Ubuntu:Pro:20.04:LTS: linux-aws-5.15 and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: btrfs: ref-verify: fix use-after-free after invalid ref action At
btrfs_ref_tree_mod() after we successfully inserted the new ref entry
(local variable &amp;#39;ref&amp;#39;) into the respective block entry&amp;#39;s rbtree (local
variable &amp;#39;be&amp;#39;), if we find an unexpected action of BTRFS_DROP_DELAYED_REF,
we error out and free the ref entry without removing it from the block
entry&amp;#39;s rbtree.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: net/smc: fix LGR and link use-after-free issue We encountered a
LGR/link use-after-free issue, which manifested as the LGR/link refcnt
reaching 0 early and entering the clear process, making resource access
unsafe.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: usb: cdc-acm: Check control transfer buffer size before access If
the first fragment is shorter than struct usb_cdc_notification, we can&amp;#39;t
calculate an expected_size.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: drm/amdgpu: avoid buffer overflow attach in
smu_sys_set_pp_table() It malicious user provides a small pptable through
sysfs and then a big…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/lsn-0119-1</guid>
    </item>
  </channel>
</rss>
