CVE-2023-53613: dax: Fix dax_mapping_release() use after free
In the Linux kernel, the following vulnerability has been resolved:
dax: Fix daxmappingrelease() use after free
A CONFIGDEBUGKOBJECTRELEASE test of removing a device-dax region provider (like modprobe -r daxhmem) yields:
kobject: 'mapping0' (ffff93eb460e8800): kobjectrelease, parent 0000000000000000 (delayed 2000) [..] DEBUGLOCKSWARNON(1) WARNING: CPU: 23 PID: 282 at kernel/locking/lockdep.c:232 lockacquire+0x9fc/0x2260 [..] RIP: 0010:lockacquire+0x9fc/0x2260 [..] Call Trace: <TASK> [..] lockacquire+0xd4/0x2c0 ? idafree+0x62/0x130 rawspinlockirqsave+0x47/0x70 ? idafree+0x62/0x130 idafree+0x62/0x130 daxmappingrelease+0x1f/0x30 devicerelease+0x36/0x90 kobjectdelayedcleanup+0x46/0x150
Due to attempting idafree() 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 daxmapping to pin its parent devdax instance until daxmappingrelease().
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-53613?
CVE-2023-53613 has been categorized as a medium severity vulnerability due to the potential for use-after-free conditions in the Linux kernel.
How do I fix CVE-2023-53613?
To resolve CVE-2023-53613, update the Linux kernel to the latest stable version that includes the patch for this vulnerability.
What impact does CVE-2023-53613 have on my system?
CVE-2023-53613 can potentially lead to system instability or arbitrary code execution if exploited.
Which versions of the Linux kernel are affected by CVE-2023-53613?
CVE-2023-53613 impacts specific versions of the Linux kernel that do not contain the fix for this vulnerability.
Is there a known exploit for CVE-2023-53613?
As of now, there is no publicly available exploit for CVE-2023-53613, but it is advisable to apply patches to prevent any potential threats.