<?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>Mon, 28 Sep 2026 21:30:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49407 — dlm: fix plock invalid read</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49407</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;dlm: fix plock invalid read&lt;/p&gt;
&lt;p&gt;This patch fixes an invalid read showed by KASAN. A unlock will allocate a
&amp;#34;struct plock_op&amp;#34; and a followed send_op() will append it to a global
send_list data structure. In some cases a followed dev_read() moves it
to recv_list and dev_write() will cast it to &amp;#34;struct plock_xop&amp;#34; and access
fields which are only available in those structures. At this point an
invalid read happens by accessing those fields.&lt;/p&gt;
&lt;p&gt;To fix this issue the &amp;#34;callback&amp;#34; field is moved to &amp;#34;struct plock_op&amp;#34; to
indicate that a cast to &amp;#34;plock_xop&amp;#34; is allowed and does the additional
&amp;#34;plock_xop&amp;#34; handling if set.&lt;/p&gt;
&lt;p&gt;Example of the KASAN output which showed the invalid read:&lt;/p&gt;
&lt;p&gt;[ 2064.296453] ==================================================================
[ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm]
[ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484
[ 2064.308168]
[ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9
[ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 2064.311618] Call Trace:
[ 2064.312218]  dump_stack_lvl+0x56/0x7b
[ 2064.313150]  print_address_description.constprop.8+0x21/0x150
[ 2064.314578]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.315610]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.316595]  kasan_report.cold.14+0x7f/0x11b
[ 2064.317674]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.318687]  dev_write+0x52b…&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;dlm: fix plock invalid read&lt;/p&gt;
&lt;p&gt;This patch fixes an invalid read showed by KASAN. A unlock will allocate a
&amp;#34;struct plock_op&amp;#34; and a followed send_op() will append it to a global
send_list data structure. In some cases a followed dev_read() moves it
to recv_list and dev_write() will cast it to &amp;#34;struct plock_xop&amp;#34; and access
fields which are only available in those structures. At this point an
invalid read happens by accessing those fields.&lt;/p&gt;
&lt;p&gt;To fix this issue the &amp;#34;callback&amp;#34; field is moved to &amp;#34;struct plock_op&amp;#34; to
indicate that a cast to &amp;#34;plock_xop&amp;#34; is allowed and does the additional
&amp;#34;plock_xop&amp;#34; handling if set.&lt;/p&gt;
&lt;p&gt;Example of the KASAN output which showed the invalid read:&lt;/p&gt;
&lt;p&gt;[ 2064.296453] ==================================================================
[ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm]
[ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484
[ 2064.308168]
[ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9
[ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 2064.311618] Call Trace:
[ 2064.312218]  dump_stack_lvl+0x56/0x7b
[ 2064.313150]  print_address_description.constprop.8+0x21/0x150
[ 2064.314578]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.315610]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.316595]  kasan_report.cold.14+0x7f/0x11b
[ 2064.317674]  ? dev_write+0x52b/0x5a0 [dlm]
[ 2064.318687]  dev_write+0x52b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49407</guid>
    </item>
    <item>
      <title>RHSA-2025:10174 — Red Hat Security Advisory: kernel security update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2025:10174</link>
      <description>&lt;p&gt;kernel: Bluetooth: Fix use after free in hci_send_acl kernel: scsi: libfc: Fix use after free in fc_exch_abts_resp() kernel: blk-mq: don&amp;#39;t touch -&amp;gt;tagset in blk_mq_get_sq_hctx kernel: dlm: fix plock invalid read Kernel: use-after-free in nfsd4_ssc_setup_dul in fs/nfsd/nfs4proc.c&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth: Fix use after free in hci_send_acl kernel: scsi: libfc: Fix use after free in fc_exch_abts_resp() kernel: blk-mq: don&amp;#39;t touch -&amp;gt;tagset in blk_mq_get_sq_hctx kernel: dlm: fix plock invalid read Kernel: use-after-free in nfsd4_ssc_setup_dul in fs/nfsd/nfs4proc.c&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2025:10174</guid>
    </item>
  </channel>
</rss>
