vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 06a8fc78367d070720af960dcecec917d3ae5f3b · < b110196fec44fe966952004bd426967c2a8fd358| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans
During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL.
From the CVE record · Linux
During loopback communication, the Linux kernel's vsock/virtio code can leave a dangling pointer in vsk->trans, potentially causing a use-after-free. The input does not specify whether an attacker can trigger it, what access they would need, or whether user interaction is required.
Engineers running Linux kernels with vsock/virtio should check their versions; affected versions are not specified.