CVE-2023-53613
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-04

Last updated on: 2026-03-17

Assigner: kernel.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().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-04
Last Modified
2026-03-17
Generated
2026-06-16
AI Q&A
2025-10-04
EPSS Evaluated
2026-06-15
NVD
CVE-2023-53613
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a use-after-free bug in the Linux kernel's dax subsystem, specifically in the dax_mapping_release() function. It occurs because the function attempts to free an ida object that has already been freed, leading to potential memory corruption or kernel instability. The issue arises from improper reference counting: devices only hold a reference on their parent while registered, but if a child needs the parent object during its release, it must hold and later drop a reference properly. The fix involves ensuring that a dax_mapping pins its parent dev_dax instance until dax_mapping_release() is called.

Impact Analysis

This vulnerability can lead to kernel crashes, memory corruption, or other unpredictable behavior in systems using the affected Linux kernel dax subsystem. Such instability can cause denial of service or potentially be exploited to escalate privileges or execute arbitrary code within the kernel context.

Detection Guidance

This vulnerability can be detected by enabling CONFIG_DEBUG_KOBJECT_RELEASE in the Linux kernel and then attempting to remove a device-dax region (for example, using the command 'modprobe -r dax_hmem'). This may produce kernel warnings and stack traces indicating use-after-free errors related to dax_mapping_release(), such as DEBUG_LOCKS_WARN_ON(1) and WARNING messages in the kernel logs. Monitoring the kernel logs (e.g., using 'dmesg' or 'journalctl -k') after such operations can help detect the issue.

Mitigation Strategies

Immediate mitigation involves ensuring that the dax_mapping pins its parent dev_dax instance until dax_mapping_release() completes, preventing use-after-free errors. Practically, avoid removing device-dax regions (e.g., avoid 'modprobe -r dax_hmem') on affected kernel versions until a patch is applied. Updating the Linux kernel to a version where this issue is fixed is the recommended long-term mitigation.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53613. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart