Cloud Hypervisor: Use-after-free in virtio-block Async I/O Completion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| cloud-hypervisor | cloud-hypervisor | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Cloudhypervisor | Cloud Hypervisor |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.138% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cloudhypervisor
Cloudhypervisor cloud Hypervisor |
|
| Vendors & Products |
Cloudhypervisor
Cloudhypervisor cloud Hypervisor |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Cloud Hypervisor is a Virtual Machine Monitor for Cloud workloads. From version 21.0 to before version 51.2, a guest can cause a use-after-free in the cloud-hypervisor process by submitting two virtio-block descriptor chains that reuse the same head_index while asynchronous block I/O is enabled (e.g. io_uring, aio). When the kernel completes the duplicate operation before the original, the completion path frees a bounce buffer that the kernel is still actively reading from or writing to, corrupting the freed memory. This issue has been patched in versions 51.2 and 52.0. | |
| Title | Cloud Hypervisor: Use-after-free in virtio-block Async I/O Completion | |
| Weaknesses | CWE-416 | |
| References |
|
|
| Metrics |
cvssV4_0
|