CVE-2023-53515

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2023-53515
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53515.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2023-53515
Downstream
Related
Published
2025-10-01T11:46:03.192Z
Modified
2026-03-20T12:33:12.339829Z
Summary
virtio-mmio: don't break lifecycle of vm_dev
Details

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 vmdev struct with devres totally breaks this protection, though. Instead of waiting for the vmdev 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 CONFIGDEBUGKOBJECT_RELEASE and unbind with sysfs.

The fix is easy, don't use devres in this case.

Found during my research about object lifetime problems.

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53515.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5
Fixed
97a2d55ead76358245b446efd87818e919196d7a
Fixed
b788ad3b2468512339c05f23692e36860264e674
Fixed
3ff54d904fafabd0912796785e53cce4e69ca123
Fixed
5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e
Fixed
af5818c35173e096085c6ae2e3aac605d3d15e41
Fixed
2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e
Fixed
55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53515.json"