CVE-2023-53613 Details
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().
A use-after-free vulnerability has been identified in the Linux kernel's Device-DAX region provider management. This issue arises when a 'mapping' device is removed, leading to a kobject release warning. The vulnerability occurs because the system attempts to free an IDA object that has already been released, causing a potential memory management error. The problem is linked to the handling of parent device references during the release process of Device-DAX mappings.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/03859868ab82d57bfdd0cea1bf31f9319a5dded0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6d24b170a9db0456f577b1ab01226a2254c016a8 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7310b84821f043dcf77d5e6aa0ad55dc1e10a11d | kernel.org | Patch |
| https://git.kernel.org/stable/c/94a85474f5e3e518bdbf8c9f51cb343d734a04f7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9c2f993b6ca903c030d58451b5bf9ea27d0d17fa | kernel.org | Patch |
| https://git.kernel.org/stable/c/f76db6781d76d8464ec2faa9752cc3fb2e4f6923 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.10, < 5.10.188 >= 5.11, < 5.15.121 >= 5.16, < 6.1.39 >= 6.2, < 6.3.13 >= 6.4, < 6.4.4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Mar 17, 2026 | Modified Analysis | [email protected] |
| Feb 5, 2026 | Initial Analysis | [email protected] |
| Oct 4, 2025 | New CVE Received | kernel.org |