LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53613 is a Linux kernel device-DAX cleanup bug. When a device-DAX region provider such as dax_hmem is removed, cleanup can reference memory ownership that was already released. The source describes a kernel warning during this path, but does not provide CVSS, real-world impact, or exploit evidence.

Executive priority

Schedule normal kernel maintenance unless device-DAX is important in production or provider removal is common operationally. Escalate if your fleet uses this subsystem heavily, because kernel memory-management bugs can affect platform stability even when exploitation details are unclear.

Technical view

The flaw is a use-after-free in dax_mapping_release(). A dax_mapping could call ida_free() after the related ida object was already freed because the child mapping did not keep the parent dev_dax object alive until release. The fix pins the parent dev_dax instance until dax_mapping_release() completes.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with device-DAX region provider code in use or available. The cited trigger involves removing a provider such as dax_hmem. The bundle does not establish remote exposure, unprivileged reachability, or specific distributions affected.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. It documents a CONFIG_DEBUG_KOBJECT_RELEASE test and kernel warning during provider removal. Treat this as a kernel memory-lifetime flaw with incomplete public impact data rather than a confirmed exploited issue.

Researcher notes

Key evidence is the upstream fix rationale, not exploit research. The vulnerable condition is parent lifetime handling during dax_mapping release. Public data lacks CVSS, CWE, attacker prerequisites, and distribution-specific fixed package versions, so validation should focus on kernel patch provenance and DAX usage.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Check distribution advisories for backported fixes before relying on version numbers alone.
  • Prioritize systems using device-DAX or dax_hmem-related functionality.
  • Limit unnecessary module removal or DAX provider changes until patched.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels across affected systems.
  • Confirm whether device-DAX region providers are enabled, loaded, or operationally required.
  • Verify vendor kernels include one of the referenced stable commits or equivalent backport.
  • Review kernel logs for DAX cleanup warnings during provider removal testing.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53613 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca, 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca, 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca, 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca, 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca, 0b07ce872a9eca1ff88c0eb7f6e92dde127d21caunaffected
LinuxLinux5.10, 0, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.