Answer in brief
CVE-2023-53515 records a High severity (CVSS 7.8) vulnerability in virtio-mmio: don't break lifecycle of vm_dev. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:-:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc6:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc7:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc8:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:4.15:rc9:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc5:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.5:rc6:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <97a2d55ead76358245b446efd87818e919196d7a || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <b788ad3b2468512339c05f23692e36860264e674 || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <3ff54d904fafabd0912796785e53cce4e69ca123 || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <af5818c35173e096085c6ae2e3aac605d3d15e41 || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e || >=7eb781b1bbb7136fe78fb8c28c1c223c61fa32b5 <55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a | 97a2d55ead76358245b446efd87818e919196d7a, b788ad3b2468512339c05f23692e36860264e674, 3ff54d904fafabd0912796785e53cce4e69ca123, 5b7d5c2dd664eb8b9a06ecbc06e28d39359c422e, af5818c35173e096085c6ae2e3aac605d3d15e41, 2dcb368fe5a8eee498ca75c93a18ce2f3b0d6a8e, 55c91fedd03d7b9cf0c5199b2eb12b9b8e95281a |
| Linux/Linuxgeneric | 4.15 | Not reported |
Published upstream
Oct 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.