# GSD-2022-1004353: tcp: Fix data-races around sysctl_tcp_base_mss.

> A data race in the Linux kernel TCP stack can lead to denial of service, requiring a kernel patch to fix.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2022

## What is GSD-2022-1004353?

GSD-2022-1004353 is a vulnerability in Kernel, published on 31 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tcp: Fix data-races around sysctl_tcp_base_mss.

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.15.58 by commit 4d7dea651b7fe0322be95054f64e3711afccc543, it was introduced in version v2.6.17 by commit 5d424d5a674f782d0659a3b66d951f412901faee. For more details please see the references link.

## Which versions are affected by GSD-2022-1004353?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2022-1004353?

No fix has been published for GSD-2022-1004353 yet. Limit exposure of the affected software until one is available.

## Is GSD-2022-1004353 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1004353 and fix it if it is affected.

What it is: GSD-2022-1004353 is a vulnerability in Kernel, published on 31 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1004353 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2022-1004353/ (Markdown: https://insights.sbomify.com/GSD-2022-1004353/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1004353

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