Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53613dax: Fix dax_mapping_release() use after free

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().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53613, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < 94a85474f5e3e518bdbf8c9f51cb343d734a04f7
    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < 9c2f993b6ca903c030d58451b5bf9ea27d0d17fa
    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < 03859868ab82d57bfdd0cea1bf31f9319a5dded0
    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < f76db6781d76d8464ec2faa9752cc3fb2e4f6923
    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < 7310b84821f043dcf77d5e6aa0ad55dc1e10a11d
    • affected 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca – < 6d24b170a9db0456f577b1ab01226a2254c016a8
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.121 – ≤ 5.15.*
    • unaffected 6.1.39 – ≤ 6.1.*
    • unaffected 6.3.13 – ≤ 6.3.*
    • unaffected 6.4.4 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53613 badge
[![CVE-2023-53613](https://cveledger.app/badge/CVE-2023-53613.svg)](https://cveledger.app/cve/CVE-2023-53613)

Record last updated .