CVE-2023-53515
virtio-mmio: don't break lifecycle of vm_dev
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.15
References 7
git.kernel.org
- stable/c/97a2d55ead76358245b446efd87818e919196d7a
- stable/c/b788ad3b2468512339c05f23692e36860264e674
- stable/c/3ff54d904fafabd0912796785e53cce4e69ca123
- stable/c/5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e
- stable/c/af5818c35173e096085c6ae2e3aac605d3d15e41
- stable/c/2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e
- stable/c/55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a