# CVE-2022-50676: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()

> A race condition in the Linux kernel RDS TCP module can cause a deadlock or lockdep warning, potentially leading to a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50676, GHSA-3p2f-fj9w-3jg5, UBUNTU-CVE-2022-50676

## What is CVE-2022-50676?

CVE-2022-50676 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()

syzbot is reporting lockdep warning at rds_tcp_reset_callbacks() [1], for
commit ac3615e7f3cffe2a ("RDS: TCP: Reduce code duplication in
rds_tcp_reset_callbacks()") added cancel_delayed_work_sync() into a section
protected by lock_sock() without realizing that rds_send_xmit() might call
lock_sock().

We don't need to protect cancel_delayed_work_sync() using lock_sock(), for
even if rds_{send,recv}_worker() re-queued this work while __flush_work()
 from cancel_delayed_work_sync() was waiting for this work to complete,
retried rds_{send,recv}_worker() is no-op due to the absence of RDS_CONN_UP
bit.

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


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

Apply the vendor's patch.

## Is CVE-2022-50676 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50676 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50676 in the wild and no public exploit code.

Affected product: Linux. 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-50676/ (Markdown: https://insights.sbomify.com/CVE-2022-50676/index.md)
```

## Sources

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

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