<?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 16:40:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53665 — md: don't dereference mddev after export_rdev()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53665</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;md: don&amp;#39;t dereference mddev after export_rdev()&lt;/p&gt;
&lt;p&gt;Except for initial reference, mddev-&amp;gt;kobject is referenced by
rdev-&amp;gt;kobject, and if the last rdev is freed, there is no guarantee that
mddev is still valid. Hence mddev should not be used anymore after
export_rdev().&lt;/p&gt;
&lt;p&gt;This problem can be triggered by following test for mdadm at very
low rate:&lt;/p&gt;
&lt;p&gt;New file: mdadm/tests/23rdev-lifetime&lt;/p&gt;
&lt;p&gt;devname=${dev0##*/}
devt=`cat /sys/block/$devname/dev`
pid=&amp;#34;&amp;#34;
runtime=2&lt;/p&gt;
&lt;p&gt;clean_up_test() {
        pill -9 $pid
        echo clear &amp;gt; /sys/block/md0/md/array_state
}&lt;/p&gt;
&lt;p&gt;trap &amp;#39;clean_up_test&amp;#39; EXIT&lt;/p&gt;
&lt;p&gt;add_by_sysfs() {
        while true; do
                echo $devt &amp;gt; /sys/block/md0/md/new_dev
        done
}&lt;/p&gt;
&lt;p&gt;remove_by_sysfs(){
        while true; do
                echo remove &amp;gt; /sys/block/md0/md/dev-${devname}/state
        done
}&lt;/p&gt;
&lt;p&gt;echo md0 &amp;gt; /sys/module/md_mod/parameters/new_array || die &amp;#34;create md0 failed&amp;#34;&lt;/p&gt;
&lt;p&gt;add_by_sysfs &amp;amp;
pid=&amp;#34;$pid $!&amp;#34;&lt;/p&gt;
&lt;p&gt;remove_by_sysfs &amp;amp;
pid=&amp;#34;$pid $!&amp;#34;&lt;/p&gt;
&lt;p&gt;sleep $runtime
exit 0&lt;/p&gt;
&lt;p&gt;Test cmd:&lt;/p&gt;
&lt;p&gt;./test --save-logs --logdir=/tmp/ --keep-going --dev=loop --tests=23rdev-lifetime&lt;/p&gt;
&lt;p&gt;Test result:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6bcb: 0000 [#4] PREEMPT SMP
CPU: 0 PID: 1292 Comm: test Tainted: G      D W          6.5.0-rc2-00121-g01e55c376936 #562
RIP: 0010:md_wakeup_thread+0x9e/0x320 [md_mod]
Call Trace:
 &amp;lt;TASK&amp;gt;
 mddev_unlock+0x1b6/0x310 [md_mod]
 rdev_attr_store+0xec/0x190 [md_mod]
 sysfs_kf…&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;md: don&amp;#39;t dereference mddev after export_rdev()&lt;/p&gt;
&lt;p&gt;Except for initial reference, mddev-&amp;gt;kobject is referenced by
rdev-&amp;gt;kobject, and if the last rdev is freed, there is no guarantee that
mddev is still valid. Hence mddev should not be used anymore after
export_rdev().&lt;/p&gt;
&lt;p&gt;This problem can be triggered by following test for mdadm at very
low rate:&lt;/p&gt;
&lt;p&gt;New file: mdadm/tests/23rdev-lifetime&lt;/p&gt;
&lt;p&gt;devname=${dev0##*/}
devt=`cat /sys/block/$devname/dev`
pid=&amp;#34;&amp;#34;
runtime=2&lt;/p&gt;
&lt;p&gt;clean_up_test() {
        pill -9 $pid
        echo clear &amp;gt; /sys/block/md0/md/array_state
}&lt;/p&gt;
&lt;p&gt;trap &amp;#39;clean_up_test&amp;#39; EXIT&lt;/p&gt;
&lt;p&gt;add_by_sysfs() {
        while true; do
                echo $devt &amp;gt; /sys/block/md0/md/new_dev
        done
}&lt;/p&gt;
&lt;p&gt;remove_by_sysfs(){
        while true; do
                echo remove &amp;gt; /sys/block/md0/md/dev-${devname}/state
        done
}&lt;/p&gt;
&lt;p&gt;echo md0 &amp;gt; /sys/module/md_mod/parameters/new_array || die &amp;#34;create md0 failed&amp;#34;&lt;/p&gt;
&lt;p&gt;add_by_sysfs &amp;amp;
pid=&amp;#34;$pid $!&amp;#34;&lt;/p&gt;
&lt;p&gt;remove_by_sysfs &amp;amp;
pid=&amp;#34;$pid $!&amp;#34;&lt;/p&gt;
&lt;p&gt;sleep $runtime
exit 0&lt;/p&gt;
&lt;p&gt;Test cmd:&lt;/p&gt;
&lt;p&gt;./test --save-logs --logdir=/tmp/ --keep-going --dev=loop --tests=23rdev-lifetime&lt;/p&gt;
&lt;p&gt;Test result:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6bcb: 0000 [#4] PREEMPT SMP
CPU: 0 PID: 1292 Comm: test Tainted: G      D W          6.5.0-rc2-00121-g01e55c376936 #562
RIP: 0010:md_wakeup_thread+0x9e/0x320 [md_mod]
Call Trace:
 &amp;lt;TASK&amp;gt;
 mddev_unlock+0x1b6/0x310 [md_mod]
 rdev_attr_store+0xec/0x190 [md_mod]
 sysfs_kf…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53665</guid>
    </item>
    <item>
      <title>RHSA-2024:2394 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2024:2394</link>
      <description>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2024:2394</guid>
    </item>
  </channel>
</rss>
