CVE-2023-53613: dax: Fix dax_mapping_release() use after free
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 03859868ab82d57bfdd0cea1bf31f9319a5dded0, 6d24b170a9db0456f577b1ab01226a2254c016a8, 7310b84821f043dcf77d5e6aa0ad55dc1e10a11d.
Low priority for now. Upgrade to Linux Linux 03859868ab82d57bfdd0cea1bf31f9319a5dded0, 6d24b170a9db0456f577b1ab01226a2254c016a8, 7310b84821f043dcf77d5e6aa0ad55dc1e10a11d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Oct 4, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.10.188
- linux linux kernel5.11 and later · before 5.15.121
- linux linux kernel5.16 and later · before 6.1.39
- linux linux kernel6.2 and later · before 6.3.13
- linux linux kernel6.4 and later · before 6.4.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before 94a85474f5e3e518bdbf8c9f51cb343d734a04f7affected · git
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before 9c2f993b6ca903c030d58451b5bf9ea27d0d17faaffected · git
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before 03859868ab82d57bfdd0cea1bf31f9319a5dded0affected · git
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before f76db6781d76d8464ec2faa9752cc3fb2e4f6923affected · git
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before 7310b84821f043dcf77d5e6aa0ad55dc1e10a11daffected · git
- 0b07ce872a9eca1ff88c0eb7f6e92dde127d21ca and later · before 6d24b170a9db0456f577b1ab01226a2254c016a8affected · git
- before 5.10not affected · semver
- 5.10.188 and later · up to and including 5.10.*not affected · semver
- 5.15.121 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.4-1 | 6.4.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53608Oct 4, 2025 · nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()31Monitor
- ← EarlierCVE-2023-53611Oct 4, 2025 · ipmi_si: fix a memleak in try_smi_init()22Monitor
- Later →CVE-2023-53614Oct 4, 2025 · mm/ksm: fix race with VMA iteration and mm_struct teardown18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 03859868ab82d57bfdd0cea1bf31f9319a5dded0 | Vendor (CNA) |
| Linux Linux | 6d24b170a9db0456f577b1ab01226a2254c016a8 | Vendor (CNA) |
| Linux Linux | 7310b84821f043dcf77d5e6aa0ad55dc1e10a11d | Vendor (CNA) |
| Linux Linux | 94a85474f5e3e518bdbf8c9f51cb343d734a04f7 | Vendor (CNA) |
| Linux Linux | 9c2f993b6ca903c030d58451b5bf9ea27d0d17fa | Vendor (CNA) |
| Linux Linux | f76db6781d76d8464ec2faa9752cc3fb2e4f6923 | Vendor (CNA) |
| debian:linux | 6.1.52-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6d24b170a9db0456f577b1ab01226a2254c016a8
- git.kernel.org/stable/c/7310b84821f043dcf77d5e6aa0ad55dc1e10a11d
- git.kernel.org/stable/c/94a85474f5e3e518bdbf8c9f51cb343d734a04f7
- git.kernel.org/stable/c/9c2f993b6ca903c030d58451b5bf9ea27d0d17fa
- git.kernel.org/stable/c/f76db6781d76d8464ec2faa9752cc3fb2e4f6923
Vendor advisories and official records. Exploit/PoC links are deliberately left out.