vsock: fix recursive ->recvmsg calls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.486.10.76.11In the Linux kernel, the following vulnerability has been resolved:
vsock: fix recursive ->recvmsg calls
After a vsock socket has been added to a BPF sockmap, its prot->recvmsg has been replaced with vsock_bpf_recvmsg(). Thus the following recursiion could happen:
vsock_bpf_recvmsg() -> __vsock_recvmsg() -> vsock_connectible_recvmsg() -> prot->recvmsg() -> vsock_bpf_recvmsg() again
We need to fix it by calling the original ->recvmsg() without any BPF sockmap logic in __vsock_recvmsg().
From the CVE record · Linux
The Linux kernel's vsock receive path can call itself recursively after a vsock socket is added to a BPF sockmap. The input does not specify what access an attacker needs, whether user interaction is required, or the resulting impact beyond recursion.
Engineers running Linux kernels with vsock and BPF sockmaps should check their versions; affected versions are not specified.