# GSD-2022-1002741: afs: Adjust ACK interpretation to try and cope with NAT

> Adjusts ACK interpretation in the Linux Kernel AFS module to handle NAT scenarios, potentially preventing connection issues.

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

## What is GSD-2022-1002741?

GSD-2022-1002741 is a vulnerability in Kernel, published on 28 Jun 2022. It can be exploited over the network.

### Official description

afs: Adjust ACK interpretation to try and cope with NAT

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.18.3 by commit f5cb5d5d60e9ded7399c6f69d10b0f2a211e3a6e. For more details please see the references link.

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

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-1002741?

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

## Is GSD-2022-1002741 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1002741 is a vulnerability in Kernel, published on 28 Jun 2022. It can be exploited over the network.
Exploitation: There is no known exploitation of GSD-2022-1002741 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-1002741/ (Markdown: https://insights.sbomify.com/GSD-2022-1002741/index.md)
```

## Sources

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

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