CVE-2023-53613
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
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.
What immediate steps should I take to mitigate this vulnerability?
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.