[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100434-CVE-2023-53613-bba8@gregkh>
Date: Sat, 4 Oct 2025 17:52:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53613: dax: Fix dax_mapping_release() use after free
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dax: Fix dax_mapping_release() use after free
A CONFIG_DEBUG_KOBJECT_RELEASE test of removing a device-dax region
provider (like modprobe -r dax_hmem) yields:
kobject: 'mapping0' (ffff93eb460e8800): kobject_release, parent 0000000000000000 (delayed 2000)
[..]
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 23 PID: 282 at kernel/locking/lockdep.c:232 __lock_acquire+0x9fc/0x2260
[..]
RIP: 0010:__lock_acquire+0x9fc/0x2260
[..]
Call Trace:
<TASK>
[..]
lock_acquire+0xd4/0x2c0
? ida_free+0x62/0x130
_raw_spin_lock_irqsave+0x47/0x70
? ida_free+0x62/0x130
ida_free+0x62/0x130
dax_mapping_release+0x1f/0x30
device_release+0x36/0x90
kobject_delayed_cleanup+0x46/0x150
Due to attempting ida_free() on an ida object that has already been
freed. Devices typically only hold a reference on their parent while
registered. If a child needs a parent object to complete its release it
needs to hold a reference that it drops from its release callback.
Arrange for a dax_mapping to pin its parent dev_dax instance until
dax_mapping_release().
The Linux kernel CVE team has assigned CVE-2023-53613 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 5.10.188 with commit 94a85474f5e3e518bdbf8c9f51cb343d734a04f7
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 5.15.121 with commit 9c2f993b6ca903c030d58451b5bf9ea27d0d17fa
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 6.1.39 with commit 03859868ab82d57bfdd0cea1bf31f9319a5dded0
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 6.3.13 with commit f76db6781d76d8464ec2faa9752cc3fb2e4f6923
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 6.4.4 with commit 7310b84821f043dcf77d5e6aa0ad55dc1e10a11d
Issue introduced in 5.10 with commit 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and fixed in 6.5 with commit 6d24b170a9db0456f577b1ab01226a2254c016a8
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53613
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/dax/bus.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/94a85474f5e3e518bdbf8c9f51cb343d734a04f7
https://git.kernel.org/stable/c/9c2f993b6ca903c030d58451b5bf9ea27d0d17fa
https://git.kernel.org/stable/c/03859868ab82d57bfdd0cea1bf31f9319a5dded0
https://git.kernel.org/stable/c/f76db6781d76d8464ec2faa9752cc3fb2e4f6923
https://git.kernel.org/stable/c/7310b84821f043dcf77d5e6aa0ad55dc1e10a11d
https://git.kernel.org/stable/c/6d24b170a9db0456f577b1ab01226a2254c016a8
Powered by blists - more mailing lists