CVE-2022-49325: tcp: add accessors to read/set tp->snd_cwnd
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS); higher than 51.1% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3308676ec525901bf1656014003c443a60730a04, 40570375356c874b1578e05c1dcc3ff7c1322dbe, 41e191fe72282e193a7744e2fc1786b23156c9e4.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3308676ec525901bf1656014003c443a60730a04, 40570375356c874b1578e05c1dcc3ff7c1322dbe, 41e191fe72282e193a7744e2fc1786b23156c9e4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 26, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-617
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.15.47
- linux linux kernel5.16 and later · before 5.17.15
- linux linux kernel5.18 and later · before 5.18.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.17affected
- 5d424d5a674f782d0659a3b66d951f412901faee and later · before 3308676ec525901bf1656014003c443a60730a04affected · git
- 5d424d5a674f782d0659a3b66d951f412901faee and later · before 5aba0ad44fb4a7fb78c5076c313456de199a3c29affected · git
- 5d424d5a674f782d0659a3b66d951f412901faee and later · before 41e191fe72282e193a7744e2fc1786b23156c9e4affected · git
- 5d424d5a674f782d0659a3b66d951f412901faee and later · before 40570375356c874b1578e05c1dcc3ff7c1322dbeaffected · git
- before 2.6.17not affected · semver
- 5.15.47 and later · up to and including 5.15.*not affected · semver
- 5.17.15 and later · up to and including 5.17.*not affected · semver
- 5.18.4 and later · up to and including 5.18.*not affected · semver
- 5.19 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49323Feb 26, 2025 · iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe()22Monitor
- ← EarlierCVE-2022-49324Feb 26, 2025 · mips: cpc: Fix refcount leak in mips_cpc_default_phys_base22Monitor
- Later →CVE-2022-49326Feb 26, 2025 · rtl818x: Prevent using not initialized queues22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3308676ec525901bf1656014003c443a60730a04 | Vendor (CNA) |
| Linux Linux | 40570375356c874b1578e05c1dcc3ff7c1322dbe | Vendor (CNA) |
| Linux Linux | 41e191fe72282e193a7744e2fc1786b23156c9e4 | Vendor (CNA) |
| Linux Linux | 5aba0ad44fb4a7fb78c5076c313456de199a3c29 | Vendor (CNA) |
| debian:linux | 5.18.5-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-31739429 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-52952483 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2025-39803201 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2023-52621337 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers31Monitor
- CVE-2026-31398401 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2026-46117456 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.