# CVE-2022-48786: vsock: remove vsock from connected table when connect is interrupted by a signal

> A race condition in the Linux kernel vsock implementation allows list corruption, potentially leading to memory corruption or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-48786, GHSA-qv99-r3jr-9wm2, RHSA-2024:10273, UBUNTU-CVE-2022-48786

## What is CVE-2022-48786?

CVE-2022-48786 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2022-48786?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bpftool` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `bpftool-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-abi-stablelists` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-core` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-core` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-devel` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-modules` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-modules-extra` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-devel` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-doc` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-modules` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-modules-extra` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-tools` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-tools-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-tools-libs` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `perf` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `perf-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `python3-perf` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `python3-perf-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `bpftool` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `bpftool-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-abi-stablelists` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-core` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-core` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-devel` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-modules` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debug-modules-extra` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo-common-aarch64` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo-common-ppc64le` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo-common-s390x` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |
| `kernel-debuginfo-common-x86_64` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:4.18.0-372.131.1.el8_6 |

Products: Linux kernel.

## How do I fix CVE-2022-48786?

Apply the vendor's patch.

## Is CVE-2022-48786 being exploited?

There is no known exploitation of CVE-2022-48786 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48786 and fix it if it is affected.

What it is: CVE-2022-48786 is a high-severity memory corruption vulnerability in Linux kernel, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48786 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48786/ (Markdown: https://insights.sbomify.com/CVE-2022-48786/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48786
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48786
- OSV: https://osv.dev/vulnerability/CVE-2022-48786

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48786/
Summaries are generated and may contain mistakes; the official description above is the record.