CVE-2022-48786
published 2024-07-16CVE-2022-48786: In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.25%
16.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
vsock_connect() expects that the socket could already be in the
TCP_ESTABLISHED state when the connecting task wakes up with a signal
pending. If this happens the socket will be in the connected table, and
it is not removed when the socket state is reset. In this situation it's
common for the process to retry connect(), and if the connection is
successful the socket will be added to the connected table a second
time, corrupting the list.
Prevent this by calling vsock_remove_connected() if a signal is received
while waiting for a connection. This is harmless if the socket is not in
the connected table, and if it is in the table then removing it will
prevent list corruption from a double add.
Note for backporting: this patch requires d5afa82c977e ("vsock: correct
removal of socket from the list"), which is in all current stable trees
except 4.9.y.
Affected
25 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.11-1 (bookworm) | linux 5.16.11-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < 0bb88f3f7e8d506f3efe46d694964117e20efbfc | 0bb88f3f7e8d506f3efe46d694964117e20efbfc |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < e3b3939fd137aab6d00d54bee0ee9244b286a608 | e3b3939fd137aab6d00d54bee0ee9244b286a608 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < 2910bcb9f67551a45397735e47b6d456eb8cd549 | 2910bcb9f67551a45397735e47b6d456eb8cd549 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < 5f326fe2aef411a6575628f92bd861463ea91df7 | 5f326fe2aef411a6575628f92bd861463ea91df7 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < 87cd1bbd6677411e17369cd4b7389ab1e1fdba44 | 87cd1bbd6677411e17369cd4b7389ab1e1fdba44 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < 787468ee7a435777521d33399d012fd591ae2f94 | 787468ee7a435777521d33399d012fd591ae2f94 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < addd62a8cb6fa90aa322365c62487da61f6baab8 | addd62a8cb6fa90aa322365c62487da61f6baab8 |
| linux | linux | >= d021c344051af91f42c5ba9fdedc176740cbd238 < b9208492fcaecff8f43915529ae34b3bcb03877c | b9208492fcaecff8f43915529ae34b3bcb03877c |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 0 < 5.16.11-1 | 5.16.11-1 |
| linux | linux_kernel | >= 3.9 < 4.9.303 | 4.9.303 |
| linux | linux_kernel | >= 4.10 < 4.14.268 | 4.14.268 |
| linux | linux_kernel | >= 4.15 < 4.19.231 | 4.19.231 |
| linux | linux_kernel | >= 4.20 < 5.4.181 | 5.4.181 |
| linux | linux_kernel | >= 5.11 < 5.15.25 | 5.15.25 |
| linux | linux_kernel | >= 5.16 < 5.16.11 | 5.16.11 |
| linux | linux_kernel | >= 5.5 < 5.10.102 | 5.10.102 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 5.16.10 vsock_connect state issue (Nessus ID 209785 / WID-SEC-2024-1625)
vuldb·2026-07-11·CVSS 5.5
CVE-2022-48786 [MEDIUM] Linux Kernel up to 5.16.10 vsock_connect state issue (Nessus ID 209785 / WID-SEC-2024-1625)
A vulnerability was found in Linux Kernel up to 5.16.10. It has been declared as problematic. Affected is the function vsock_connect. The manipulation results in state issue.
This vulnerability was named CVE-2022-48786. The attack needs to be approached within the local network. There is no available exploit.
It is recommended to upgrade the affected component.
GHSA
GHSA-qv99-r3jr-9wm2: In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
ghsa_unreviewed·2024-07-16
CVE-2022-48786 [MEDIUM] GHSA-qv99-r3jr-9wm2: In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
vsock_connect() expects that the socket could already be in the
TCP_ESTABLISHED state when the connecting task wakes up with a signal
pending. If this happens the socket will be in the connected table, and
it is not removed when the socket state is reset. In this situation it's
common for the process to retry connect(), and if the connection is
successful the socket will be added to the connected table a second
time, corrupting the list.
Prevent this by calling vsock_remove_connected() if a signal is received
while waiting for a connection. This is harmless if the socket is not in
the connected table, and if it is in the table then removing
OSV
CVE-2022-48786: In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal v
osv·2024-07-16·CVSS 5.5
CVE-2022-48786 [MEDIUM] CVE-2022-48786: In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal v
In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal vsock_connect() expects that the socket could already be in the TCP_ESTABLISHED state when the connecting task wakes up with a signal pending. If this happens the socket will be in the connected table, and it is not removed when the socket state is reset. In this situation it's common for the process to retry connect(), and if the connection is successful the socket will be added to the connected table a second time, corrupting the list. Prevent this by calling vsock_remove_connected() if a signal is received while waiting for a connection. This is harmless if the socket is not in the connected table, and if it is in the table then removing it
Red Hat
kernel: vsock: remove vsock from connected table when connect is interrupted by a signal
vendor_redhat·2024-07-16·CVSS 5.5
CVE-2022-48786 [MEDIUM] CWE-371 kernel: vsock: remove vsock from connected table when connect is interrupted by a signal
kernel: vsock: remove vsock from connected table when connect is interrupted by a signal
In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
vsock_connect() expects that the socket could already be in the
TCP_ESTABLISHED state when the connecting task wakes up with a signal
pending. If this happens the socket will be in the connected table, and
it is not removed when the socket state is reset. In this situation it's
common for the process to retry connect(), and if the connection is
successful the socket will be added to the connected table a second
time, corrupting the list.
Prevent this by calling vsock_remove_connected() if a signal is received
while waiting for a connection. This is harmle
Debian
CVE-2022-48786: linux - In the Linux kernel, the following vulnerability has been resolved: vsock: remo...
vendor_debian·2022·CVSS 5.5
CVE-2022-48786 [MEDIUM] CVE-2022-48786: linux - In the Linux kernel, the following vulnerability has been resolved: vsock: remo...
In the Linux kernel, the following vulnerability has been resolved: vsock: remove vsock from connected table when connect is interrupted by a signal vsock_connect() expects that the socket could already be in the TCP_ESTABLISHED state when the connecting task wakes up with a signal pending. If this happens the socket will be in the connected table, and it is not removed when the socket state is reset. In this situation it's common for the process to retry connect(), and if the connection is successful the socket will be added to the connected table a second time, corrupting the list. Prevent this by calling vsock_remove_connected() if a signal is received while waiting for a connection. This is harmless if the socket is not in the connected table, and if it is in the table then removing it
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0bb88f3f7e8d506f3efe46d694964117e20efbfchttps://git.kernel.org/stable/c/2910bcb9f67551a45397735e47b6d456eb8cd549https://git.kernel.org/stable/c/5f326fe2aef411a6575628f92bd861463ea91df7https://git.kernel.org/stable/c/787468ee7a435777521d33399d012fd591ae2f94https://git.kernel.org/stable/c/87cd1bbd6677411e17369cd4b7389ab1e1fdba44https://git.kernel.org/stable/c/addd62a8cb6fa90aa322365c62487da61f6baab8https://git.kernel.org/stable/c/b9208492fcaecff8f43915529ae34b3bcb03877chttps://git.kernel.org/stable/c/e3b3939fd137aab6d00d54bee0ee9244b286a608https://git.kernel.org/stable/c/0bb88f3f7e8d506f3efe46d694964117e20efbfchttps://git.kernel.org/stable/c/2910bcb9f67551a45397735e47b6d456eb8cd549https://git.kernel.org/stable/c/5f326fe2aef411a6575628f92bd861463ea91df7https://git.kernel.org/stable/c/787468ee7a435777521d33399d012fd591ae2f94https://git.kernel.org/stable/c/87cd1bbd6677411e17369cd4b7389ab1e1fdba44https://git.kernel.org/stable/c/addd62a8cb6fa90aa322365c62487da61f6baab8https://git.kernel.org/stable/c/b9208492fcaecff8f43915529ae34b3bcb03877chttps://git.kernel.org/stable/c/e3b3939fd137aab6d00d54bee0ee9244b286a608
2024-07-16
Published