CVE-2023-53515 | virtio-mmio: don't break lifecycle of vm_dev

In the Linux kernel, the following vulnerability has been resolved: virtio-mmio: don't break lifecycle of vm_dev vm_dev has a separate lifecycle because it has a 'struct device' embedded. Thus, having a release callback for it is correct. Allocating the vm_dev struct with devres totally breaks this protection, though. Instead of waiting for the vm_dev release callback, the memory is freed when the platform_device is removed. Resulting in a use-after-free when finally the callback is to be called. To easily see the problem, compile the kernel with CONFIG_DEBUG_KOBJECT_RELEASE and unbind with sysfs. The fix is easy, don't use devres in this case. Found during my research about object lifetime problems.

Published: 2025-10-01 Last update: 2026-04-06 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-53515 is rated Low Risk (33.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-53515

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-01 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-53515

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2023-53515

OS Trackers for CVE-2023-53515

vendor priority summary link
debian not yet assigned CVE-2023-53515 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-53515
redhat medium — https://access.redhat.com/security/cve/CVE-2023-53515
suse medium — https://www.suse.com/security/cve/CVE-2023-53515/
ubuntu medium CVE-2023-53515 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 159, released 138, not-affected 84, needed 15, needs-triage 1. https://ubuntu.com/security/CVE-2023-53515

Affected software / configurations for CVE-2023-53515

Vendor Product Version Raw CPE
linux linux_kernel >= 4.15.1, < 4.19.293 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 4.20, < 5.4.255 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.5, < 5.10.192 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.128 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.47 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.4.12 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:-:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc3:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc4:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc5:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc6:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc7:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc8:*:*:*:*:*:*
linux linux_kernel 4.15 cpe:2.3:o:linux:linux_kernel:4.15:rc9:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc1:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc2:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc4:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc5:*:*:*:*:*:*
linux linux_kernel 6.5 cpe:2.3:o:linux:linux_kernel:6.5:rc6:*:*:*:*:*:*

References for CVE-2023-53515

cvelogic Threat Intelligence