# CVE-2022-49325: tcp: add accessors to read/set tp->snd_cwnd

> A bug in the Linux kernel TCP implementation could trigger a warning or crash due to invalid congestion window values, potentially causing 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:** 26 Feb 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-49325, GHSA-qwqp-8pr4-72vm, ROOT-OS-DEBIAN-11-CVE-2022-49325, UBUNTU-CVE-2022-49325

## What is CVE-2022-49325?

CVE-2022-49325 is a high-severity denial of service vulnerability in Linux kernel, published on 26 Feb 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:

tcp: add accessors to read/set tp->snd_cwnd

We had various bugs over the years with code
breaking the assumption that tp->snd_cwnd is greater
than zero.

Lately, syzbot reported the WARN_ON_ONCE(!tp->prior_cwnd) added
in commit 8b8a321ff72c ("tcp: fix zero cwnd in tcp_cwnd_reduction")
can trigger, and without a repro we would have to spend
considerable time finding the bug.

Instead of complaining too late, we want to catch where
and when tp->snd_cwnd is set to an illegal value.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-49325 being exploited?

There is no known exploitation of CVE-2022-49325 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-49325 and fix it if it is affected.

What it is: CVE-2022-49325 is a high-severity denial of service vulnerability in Linux kernel, published on 26 Feb 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-49325 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-49325/ (Markdown: https://insights.sbomify.com/CVE-2022-49325/index.md)
```

## Sources

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

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