<?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 15:09:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49176 — bfq: fix use-after-free in bfq_dispatch_request</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49176</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;bfq: fix use-after-free in bfq_dispatch_request&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free report when doing normal scsi-mq test&lt;/p&gt;
&lt;p&gt;[69832.239032] ==================================================================
[69832.241810] BUG: KASAN: use-after-free in bfq_dispatch_request+0x1045/0x44b0
[69832.243267] Read of size 8 at addr ffff88802622ba88 by task kworker/3:1H/155
[69832.244656]
[69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-10295-g576c6382529e #8
[69832.246626] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[69832.249069] Workqueue: kblockd blk_mq_run_work_fn
[69832.250022] Call Trace:
[69832.250541]  dump_stack+0x9b/0xce
[69832.251232]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.252243]  print_address_description.constprop.6+0x3e/0x60
[69832.253381]  ? __cpuidle_text_end+0x5/0x5
[69832.254211]  ? vprintk_func+0x6b/0x120
[69832.254994]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.255952]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.256914]  kasan_report.cold.9+0x22/0x3a
[69832.257753]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.258755]  check_memory_region+0x1c1/0x1e0
[69832.260248]  bfq_dispatch_request+0x1045/0x44b0
[69832.261181]  ? bfq_bfqq_expire+0x2440/0x2440
[69832.262032]  ? blk_mq_delay_run_hw_queues+0xf9/0x170
[69832.263022]  __blk_mq_do_dispatch_sched+0x52f/0x830
[69832.264011]  ? blk_mq_sched_request_inserted…&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;bfq: fix use-after-free in bfq_dispatch_request&lt;/p&gt;
&lt;p&gt;KASAN reports a use-after-free report when doing normal scsi-mq test&lt;/p&gt;
&lt;p&gt;[69832.239032] ==================================================================
[69832.241810] BUG: KASAN: use-after-free in bfq_dispatch_request+0x1045/0x44b0
[69832.243267] Read of size 8 at addr ffff88802622ba88 by task kworker/3:1H/155
[69832.244656]
[69832.245007] CPU: 3 PID: 155 Comm: kworker/3:1H Not tainted 5.10.0-10295-g576c6382529e #8
[69832.246626] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
[69832.249069] Workqueue: kblockd blk_mq_run_work_fn
[69832.250022] Call Trace:
[69832.250541]  dump_stack+0x9b/0xce
[69832.251232]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.252243]  print_address_description.constprop.6+0x3e/0x60
[69832.253381]  ? __cpuidle_text_end+0x5/0x5
[69832.254211]  ? vprintk_func+0x6b/0x120
[69832.254994]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.255952]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.256914]  kasan_report.cold.9+0x22/0x3a
[69832.257753]  ? bfq_dispatch_request+0x1045/0x44b0
[69832.258755]  check_memory_region+0x1c1/0x1e0
[69832.260248]  bfq_dispatch_request+0x1045/0x44b0
[69832.261181]  ? bfq_bfqq_expire+0x2440/0x2440
[69832.262032]  ? blk_mq_delay_run_hw_queues+0xf9/0x170
[69832.263022]  __blk_mq_do_dispatch_sched+0x52f/0x830
[69832.264011]  ? blk_mq_sched_request_inserted…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49176</guid>
    </item>
    <item>
      <title>LSN-0114-1 — Kernel Live Patch Security Notice</title>
      <link>https://vulnerability.circl.lu/vuln/lsn-0114-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, 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 and 22 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: bfq: fix use-after-free in bfq_dispatch_request KASAN reports a
use-after-free report when doing normal scsi-mq test .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: block, bfq: don&amp;#39;t move oom_bfqq Our test report a UAF: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() When
l2cap_recv_frame() is invoked to receive data, and the cid is
L2CAP_CID_A2MP, if the channel does not exist, it will create a channel.
However, after a channel is created, the hold operation of the channel is
not performed.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: SUNRPC: Fix UAF in svc_tcp_listen_data_ready() After the listener
svc_sock is freed, and before invoking svc_tcp_accept() for the established
child sock, there is a window that the newsock retaining a freed listener
svc_sock in sk_user_data which cloning from parent.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin
mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated
in ext4_ext_create_new_leaf(), we&amp;#39;ll use the stale path and cause UAF.
Below is a sample trace with dummy values: ext4_ext_insert_extent path .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy
and Mbo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, 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 and 22 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: bfq: fix use-after-free in bfq_dispatch_request KASAN reports a
use-after-free report when doing normal scsi-mq test .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: block, bfq: don&amp;#39;t move oom_bfqq Our test report a UAF: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() When
l2cap_recv_frame() is invoked to receive data, and the cid is
L2CAP_CID_A2MP, if the channel does not exist, it will create a channel.
However, after a channel is created, the hold operation of the channel is
not performed.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: SUNRPC: Fix UAF in svc_tcp_listen_data_ready() After the listener
svc_sock is freed, and before invoking svc_tcp_accept() for the established
child sock, there is a window that the newsock retaining a freed listener
svc_sock in sk_user_data which cloning from parent.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin
mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated
in ext4_ext_create_new_leaf(), we&amp;#39;ll use the stale path and cause UAF.
Below is a sample trace with dummy values: ext4_ext_insert_extent path .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy
and Mbo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/lsn-0114-1</guid>
    </item>
  </channel>
</rss>
