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.

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity High

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00024.

Key SSVC decision points have not yet been added.

Affected Vendors & Products

Vendors Products
Linux
  • Linux Kernel

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

Vendors Products
Linux
  • Linux Kernel
References
Link Providers
https://git.kernel.org/stable/c/2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e cve-icon cve-icon
https://git.kernel.org/stable/c/3ff54d904fafabd0912796785e53cce4e69ca123 cve-icon cve-icon
https://git.kernel.org/stable/c/55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a cve-icon cve-icon
https://git.kernel.org/stable/c/5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e cve-icon cve-icon
https://git.kernel.org/stable/c/97a2d55ead76358245b446efd87818e919196d7a cve-icon cve-icon
https://git.kernel.org/stable/c/af5818c35173e096085c6ae2e3aac605d3d15e41 cve-icon cve-icon
https://git.kernel.org/stable/c/b788ad3b2468512339c05f23692e36860264e674 cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2025100131-CVE-2023-53515-abe8@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2023-53515 cve-icon
https://www.cve.org/CVERecord?id=CVE-2023-53515 cve-icon
History

Thu, 02 Oct 2025 09:00:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Vendors & Products Linux
Linux linux Kernel

Thu, 02 Oct 2025 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Wed, 01 Oct 2025 12:00:00 +0000

Type Values Removed Values Added
Description 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.
Title virtio-mmio: don't break lifecycle of vm_dev
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2025-10-01T11:46:03.192Z

Reserved: 2025-10-01T11:39:39.406Z

Link: CVE-2023-53515

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-10-01T12:15:55.583

Modified: 2025-10-02T19:11:46.753

Link: CVE-2023-53515

cve-icon Redhat

Severity : Important

Publid Date: 2025-10-01T00:00:00Z

Links: CVE-2023-53515 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2025-10-02T08:38:34Z