CVE-2022-48786

published 16 Jul 2024 · updated 5 Aug 2026

vsock: remove vsock from connected table when connect is interrupted by a signal

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0bb88f3f7e8d506f3efe46d694964117e20efbfc, Kernel 2910bcb9f67551a45397735e47b6d456eb8cd549, Kernel 5f326fe2aef411a6575628f92bd861463ea91df7 and 5 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.9, >=d021c344051af91f42c5ba9fdedc176740cbd238 <0bb88f3f7e8d506f3efe46d694964117e20efbfc, >=d021c344051af91f42c5ba9fdedc176740cbd238 <2910bcb9f67551a45397735e47b6d456eb8cd549, >=d021c344051af91f42c5ba9fdedc176740cbd238 <5f326fe2aef411a6575628f92bd861463ea91df7, >=d021c344051af91f42c5ba9fdedc176740cbd238 <787468ee7a435777521d33399d012fd591ae2f94, >=d021c344051af91f42c5ba9fdedc176740cbd238 <87cd1bbd6677411e17369cd4b7389ab1e1fdba44, >=d021c344051af91f42c5ba9fdedc176740cbd238 <addd62a8cb6fa90aa322365c62487da61f6baab8, >=d021c344051af91f42c5ba9fdedc176740cbd238 <b9208492fcaecff8f43915529ae34b3bcb03877c, >=d021c344051af91f42c5ba9fdedc176740cbd238 <e3b3939fd137aab6d00d54bee0ee9244b286a6080bb88f3f7e8d506f3efe46d694964117e20efbfc, 2910bcb9f67551a45397735e47b6d456eb8cd549, 5f326fe2aef411a6575628f92bd861463ea91df7, 787468ee7a435777521d33399d012fd591ae2f94, 87cd1bbd6677411e17369cd4b7389ab1e1fdba44, addd62a8cb6fa90aa322365c62487da61f6baab8, b9208492fcaecff8f43915529ae34b3bcb03877c, e3b3939fd137aab6d00d54bee0ee9244b286a608

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-48786 severity on Zeptric[![CVE-2022-48786](https://zeptric.io/badge/cve/CVE-2022-48786.svg)](https://zeptric.io/cve/CVE-2022-48786)